Skip to content
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

Automatically create and update running PR with changes from slack-api-ref #456

Closed
duffn opened this issue Mar 24, 2023 · 2 comments · Fixed by #458
Closed

Automatically create and update running PR with changes from slack-api-ref #456

duffn opened this issue Mar 24, 2023 · 2 comments · Fixed by #458
Labels

Comments

@duffn
Copy link
Contributor

duffn commented Mar 24, 2023

Every once in awhile there's a PR like this where somebody manually updates the codebase from slack-api-ref by running the update Rake task. #455

What about some automated process that runs maybe once per day (sometime after slack-api-ref), runs the Rake task, and creates or updates a PR in this repo with the changes generated.

  • New changes but no PR -> open a PR with the changes
  • New changes with already existing PR -> update the PR with the new changes
  • No changes -> do nothing

This wouldn't actually merge anything to the main branch, but just maintain a running PR with changes from slack-api-ref. Maintainers of the repo could then merge the PR whenever they like. I'm thinking that this is something like the running PRs from https://github.com/googleapis/release-please

@dblock
Copy link
Collaborator

dblock commented Mar 25, 2023

Love it. Add an automatic update of CHANGELOG (either simple that says "updated Slack API to [date]" or fancy "added x, y, z method" and those PRs will be mergeable. Also see #10 that was in that spirit.

@dblock dblock added the chore label Mar 25, 2023
@duffn
Copy link
Contributor Author

duffn commented Mar 25, 2023

Great. I'll take a go at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants