Add workflow overview #19
Open
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
ThoFrank
force-pushed
the
workflow_overview
branch
from
44bcf0a to
52d0f98
Compare
Signed-off-by: Thomas Frank <[email protected]>
Signed-off-by: Thomas Frank <[email protected]>
Signed-off-by: Thomas Frank <[email protected]>
ThoFrank
force-pushed
the
workflow_overview
branch
from
52d0f98 to
3f7de35
Compare
|
Also added the trigger conditions for the merge queue. I am currently trying to find out how to reference the individual checks in otterdog. |
Signed-off-by: Thomas Frank <[email protected]>
|
We tried to capture the rules how GitHub references jobs to status checks here: https://otterdog.readthedocs.io/en/latest/reference/organization/repository/status-check/ |
|
I looked at that page already. Probably it's a good idea to just use unique names for all jobs. |
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.
Visualization of our GH action strategy.
depends on:
#18 ✅ to prepare for code coverage and doxygen
#12 ✅ for Code coverage
#20 ✅ for doxygen