-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Constant branch name #18
Conversation
…anch multiple times
I am not quite sure if this change could lead to unexpected consequences, but I'm gladly willing to try.
|
…on integration, following #18 Signed-off-by: Jaid <jaid.jsx@gmail.com>
I'll add the user's choice between a constant branch name and a randomly generated branch name later this day. |
New change based on this pull request: Constant branch name is the new default now. - name: Jaid/action-sync-node-meta
uses: jaid/action-sync-node-meta@v2.0.0
with:
githubToken: ${{ secrets.GITHUB_TOKEN }}
branch: action-sync-node-meta Random addition is optional. - name: Jaid/action-sync-node-meta
uses: jaid/action-sync-node-meta@v2.0.0
with:
githubToken: ${{ secrets.GITHUB_TOKEN }}
branch: action-sync-node-meta_{random} |
@Jaid even better |
I think it makes more sense to use a constant branch + PR and update it. This way we do not have multiple PRs in case the metadata change more often.
We need to have these PRs fixed for this: