Commit and upload only on bundesAPI-repos (Deutschland Workflow) #4
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
Member
Author
|
Maybe we could also link this action the |
Member
Author
|
@wirthual what do you think? If someone wants to use the upload, they could revert this setting here. But I think at the moment most of the time the code should only be uploaded if the repo is part of bundesapi. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As used in bundesAPI/pegel-online-api#6 only commit and upload Python-Client code if the repo is from bundesAPI.
This should help especially while working on forks to keep the code cleaner without too many generations and commits of client code.