Commit Graph

5 Commits (master)

Author SHA1 Message Date
zowoq 8917ffe723 .github/workflows/merge-staging.yml: change condition to `repository_owner`
This is consistent with the other actions.
2021-05-28 08:10:53 +10:00
Jan Tojnar 6225647cfc
.github/workflows/merge-staging.yml: Include branch in comment
If I receive the mail notification that staging(-next) merge failed,
I either need to check `git log staging-next` or click the action run link
to find out where should I resolve the conflict.

To save time, let’s include the information about which step failed right in the comment.
2021-05-13 13:58:14 +02:00
Frederik Rietdijk d24639b341 GH action: merge staging(-next): fix cron
It went every minute past every 6th hour, which was too often.
Now it should go on the zeroth minute every 6th hour.
2020-12-02 14:25:08 +01:00
Frederik Rietdijk 318f929047 GH Action: merge staging(-next): comment on failure
Comment on the designated issue in case of a failure.

Whoever wants to help out resolving merge conflicts can simply follow
this issue.
2020-11-29 13:19:51 +01:00
Frederik Rietdijk 24884e5aac GH Action: merge staging(-next) periodically
Automate the merging of `master` -> `staging-next` -> `staging`.

Our main development branch is `master`. Large rebuilds go to `staging`.
Periodically, `staging` is merged into `staging-next` for stabilization.
When considered sufficiently stable, `staging-next` is merged into
`master`.

As changes arrive on these branches, it is important that they're all
updated regularly with eachothers changes. This commit automates that
part.
2020-11-28 13:44:18 +01:00