Remove requirements.txt and correct workflow triggers
#87
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
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.
Changes introduced with this PR
Since the
requirements.txtfile is generated during the build, there is no need to commit it to the repo. Moreover, doing so distracts the Renovate bot, making maintenance harder and occasionally awkward. This PR removes it from the repo so that new plugins created from this template won't acquire this useless file.This PR also tweaks the workflow triggers so that they trigger for pull request updates, updates to the
mainbranch and for tag creations, and not for updates to any upstream branch. This will avoid the CI running twice when a PR refers to an upstream branch.By contributing to this repository, I agree to the contribution guidelines.