Skip to content

Conversation

roblarsen
Copy link
Member

@roblarsen roblarsen commented Sep 9, 2025

Revisiting the old issue of not being able to build to a protected branch. Why not just have the bot create a PR?

#2803

@roblarsen
Copy link
Member Author

It works....

image

roblarsen#2

@roblarsen roblarsen requested a review from coliff September 9, 2025 18:55
@roblarsen roblarsen added the github_actions Pull requests that update Github_actions code label Sep 9, 2025
@roblarsen roblarsen changed the title trying this a different way! Updating dist via GitHub Actions and an automated PR Sep 10, 2025
@roblarsen
Copy link
Member Author

@coliff This is worth a look now

Changed actions/checkout and actions/setup-node to reference specific commit SHAs for improved security and reproducibility. Also set 'persist-credentials' to false for checkout.
@coliff
Copy link
Member

coliff commented Sep 11, 2025

Hmm... Making a separate PR afterwards seems like it'd create extra noise. Would it be better to run on any PRs which are affected (changes to /src folder or something) and push a commit to that PR?
And of this were to be merged as it is, what's the process for contributors -should they still update dist/ themselves in their PR or would that be added to .gitignore or what?

@roblarsen
Copy link
Member Author

I believe, and I can test this, that if there are not changes for dist after the build there will be no noise. So if the person submitting the PR does a build there should be no changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions Pull requests that update Github_actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants