Support updates #709
Merged
Support updates #709
Conversation
This file contains hidden or 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
I also think we should probably keep consistency over viz and comp, but don't have strong opinions. |
anissa111
approved these changes
Apr 1, 2025
jukent
approved these changes
Apr 1, 2025
|
Alright, in that case I'll go ahead and merge and make the corresponding changes on viz. If we feel like dropping the support page and moving to links in the future - not opposed. |
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.
PR Summary
The motivation for this PR was to remove the reference to the old ncar/geocat repo as a suggested support mechanism. I opted to do that by adjusting the language and recommendations on our longer format support page. This allows us to keep that additional content, but isn't consistent with the simplified approach used in geocat-applications or geocat-examples that just links out to GitHub issues and the GeoCAT suggestion box. I'm inclined to keep at least viz and comp consistent, but don't have too strong of an opinion otherwise. Curious what others think.
Currently, this PR does the following:
Related Tickets & Documents
Closes #706
PR Checklist
General
docs/release-notes.rstin a relevant section for the upcoming release.