Closed stain closed 6 years ago
Marked as discuss
- we can keep this simple or general (or something in-between)
I agree, we shouldn't bake in a commercial third party into the BCO spec/standard
Thanks for clarifying, @HadleyKing but I think the example should be updated to match Stian's suggestion.
github_extension
to scm_extension
[x] user_guide.md:520: "github_extension": {
[x] extension-github.md:9: "github_extension": {
[x] antiviral_resistance_detectionTypeDef.json:23: "github_extension": {
[x] HCV1a.json:91: "github_extension": {
[x] bco-domains.md:22: "github_extension": {
[x] README.md:46: * GitHub extension
[x] bco-domains.md:74:* GitHub extension
The github extension is only explained by example.
The two keys
github_repository
andgithub_URI
are not explained and seem to be partially overlapping. Thecamel_Case
is also inconsistent.Given that these are URLs I think the extension should support any source control repository, not just github.com, perhaps something like:
Here's how Maven defines it's scm metadata.