Take the staging project prjconf from the test branch #1787
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
See #1781 (comment) for the suggestion The idea is that the staging project's source of truth should be the $os-$num branch, not only for the package sources, but also for the prjconf. The only caveat is, that changes in the prjconf don't carry over to the deployment branch, but I guess we can live with that for now 🤷
dirkmueller
approved these changes
Oct 1, 2024
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.
See #1781 (comment) for the suggestion
The idea is that the staging project's source of truth should be the
$os-$numbranch, not only for the package sources, but also for theprjconf. The only caveat is, that changes in theprjconfdon't carry over to the deployment branch, but I guess we can live with that for now 🤷