Add API warning #1613
Merged
Add API warning #1613
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
Signed-off-by: brycegbrazen <[email protected]>
maxnbk
approved these changes
Jan 18, 2024
instinct-vfx
approved these changes
Jan 18, 2024
Signed-off-by: brycegbrazen <[email protected]>
Signed-off-by: Jean-Christophe Morin <[email protected]>
Signed-off-by: Jean-Christophe Morin <[email protected]>
JeanChristopheMorinPerso
merged commit 7c2bd04
into
AcademySoftwareFoundation:main
5 checks passed
Pixel-Minions
pushed a commit
to Pixel-Minions/rez
that referenced
this pull request
Feb 14, 2024
…on#1613) Signed-off-by: brycegbrazen <[email protected]> Signed-off-by: Jose Enriquez <[email protected]>
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.
Adds info about API compatibility promises, as well as helpful info regarding when to use the Python API vs CLI.
From discussions in this thread.
This should be discussed further in the upcoming 1/18/24 meeting, but wanted to start a PR for further discussion.