657 bot updates scheduled #663
Conversation
…om checkout (github.head_ref), which would be head of current branch, not neccessarily develop (though that seems like a logical defaul). (2) commits to a new branch (specified: github.head_ref), but 2a - will it create a PR for it? 2b - with it have issues making the second commit to the same new branch?
…heduled Update to develop
|
This will need to be merged before we can really do much more testing. Update: Was able to confirm on a fork that this workflow (triggered from workflow_dispatch on develop) will create a branch from where we want (origin/develop), create a second commit on the same branch if needed for example data, but will not create a PR for that branch when it is done (just the branch). |
|
Was able to further confirm later commits will be made to the same branch, i.e., if we don't get around to merging a branch from a scheduled run before it runs again the commit will be made on the existing branch without issue. |
|
Is it possible to make this create a PR from the branch with the maintenance updates automatically? Will this run weekly or still daily? |
Yes, scoping how much of a lift that will be.
Currently set to run nightly, figured that would be helpful to troubleshooting in the next 24hours. Also note that it won't create a new branch, just continues to update. Easy to change it to weekly but would need to know what day of the week? |
Initial attempt to add scheduled workflow for file maintenance tasks.