README.md, add repo types and branching model - #38
Open
jonenst wants to merge 3 commits into
Open
Conversation
Signed-off-by: Jon Harper <jon.harper87@gmail.com>
olperr1
requested changes
Mar 20, 2025
Co-authored-by: Olivier Perrin <olivier.perrin@rte-france.com> Signed-off-by: Jon Harper <jon.harper87@gmail.com>
Collaborator
Author
|
@olperr1 I applied your proposed typo fix ti -> tip |
Collaborator
Author
|
@khouadrired is the docs for the release cycles still consistent with your latest changes on splitting in 2 ? |
Signed-off-by: HARPER Jon <jon.harper87@gmail.com>
Contributor
@jonenst for the the backend-apps and frontend-apps we have the prepare-release workflow that create the branche then we call the release workflow |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
NO
What kind of change does this PR introduce?
Docs
Other information: