jbang-catalog repository name(s)

[wfouche]

The jbang-catalog name is fixed at the moment, and can only be called that.

Receiving some pushback from the Asciidoctor project at the moment about calling the JBang commands repo jbang-catalog. They prefix all their repos with asciidoctor- so ideally for them the repo should be called asciidoctor-jbang-catalog.

• https://asciidoctor.zulipchat.com/#narrow/channel/347144-ideas-.F0.9F.92.AD/topic/Making.20AsciidoctorJ.20available.20to.20users.20via.20JBang/with/526917967

JBang could be modified to support the following for command jbang asciidoctorj@asciidoctor

• Look for repo jbang-catalog in github.com/asciidoctor.
• If this repo do not exist look for asciidoctor-jbang-catalog.

In general fallback to <account-name>-jbang-catalog if jbang-catalog does not exist for jbang run command@<account-name>.

This would actually solve a long-standing problem I have been facing, which is if you checkout multiple jbang catalogs from different projects; you have to rename them when they are cloned. Tedious.

One could argue that this naming convention should have be been used from the start: catalog repository name = <account-name>-jbang-catalog

[maxandersen]

at first I was not liking it as it would double the needed lookups to fail (we go through github, gitlab, bitbucket) - but I do actually think there is something to have it be /-jbang-catalog

To the extent I would go for making what we look for first (*)

wdyt @quintesse ?

(*) - first because its more specific and existing repos can simply rename their catalog and existing and old jbang will continue to work as at least github handles redirects.

[quintesse]

I understand this might be useful in a very limited set of circumstances and I can't think of any major downsides, so sure.

And as long as people can still use the current version, otherwise orgs like "codacy-open-source-projects-scans" might become upset that'd have to add a "codacy-open-source-projects-scans-jbang-catalog" repo 🤣

It might be important to check that we can still do our searches for catalogs for our app store, though.

[maxandersen]

searches is after jbang-catalog.json so not affecting that.

[maxandersen]

@wfouche wanna make a PR for it ? lets see how good or bad it gets ? I don't think it should be too much change to support....but can also see there could be some edge cases we haven't thought about before we actually see it work.