Convert branch scheme from dev/master to main #1250
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`ollections` -> `Collections`
docs: fix collectionless item title in catalog example
Fix a typo in collection-spec.md
Minor punctuation fix in best practices
Co-authored-by: Matthew Hanson <[email protected]>
`proj:epsg` should be summarised as an array of all values, not a Range Object, per [stac-fields](https://github.com/stac-utils/stac-fields/blob/v1.0.0-beta.10/fields.json#L575) and [other examples](https://github.com/radiantearth/stac-spec/blob/v1.0.0/examples/collection-only/collection.json#L90).
Co-authored-by: Matthew Hanson <[email protected]> Co-authored-by: Chris Holmes <[email protected]>
There was some confusing language about when `self` links should be used. This commit fixes the language in the "Use of links" section of the best practices document, and updates the wording in the item spec to reference the best practices section.
Minor spelling changes
fix(examples): change epsg summary example to an array of all values
…dations Reword recommendations around `self` links in the item spec
* update code of conduct to v2.1
…t-practices Fix typos
Update dev to include recent changes on master
… in the corresponding root catalog. (radiantearth#1209)
* Keywords in common metadata * Added keywords in simple example * Minor alignment and clarification --------- Co-authored-by: Matthias Mohr <[email protected]>
Spelling corrections
Fix media type in example
…e-and-format update ci node to 18 and format all files
|
Converting to draft until 1.1 is released |
m-mohr
requested changes
Aug 5, 2024
There was a problem hiding this comment.
This would break a lot of incoming links, e.g. all links in extensions that link to the extension maturity. Updating all links is a big maintenance overhead, so we can only merge this is someone volunteers to do all the updates in external STAC-related repositories, too. I think I'd prefer to keep the master naming of the branches at least in stac-spec...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue(s):
Proposed Changes:
PR Checklist:
or a CHANGELOG entry is not required.
and I have opened issue/PR #XXX to track the change.