| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* build(deps): bump zeebe-io/backport-action
Bumps [zeebe-io/backport-action](https://github.com/zeebe-io/backport-action) from 2b994724142df0774855690db56bc6308fb99ffa to 0.0.5. This release includes the previously tagged commit.
- [Release notes](https://github.com/zeebe-io/backport-action/releases)
- [Commits](https://github.com/zeebe-io/backport-action/compare/2b994724142df0774855690db56bc6308fb99ffa...e5d4d7c39c94b65670847d11d259b2f574fa3d30)
---
updated-dependencies:
- dependency-name: zeebe-io/backport-action
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: zowoq <59103226+zowoq@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/cachix-action](https://github.com/cachix/cachix-action) from 9 to 10.
- [Release notes](https://github.com/cachix/cachix-action/releases)
- [Commits](https://github.com/cachix/cachix-action/compare/v9...v10)
---
updated-dependencies:
- dependency-name: cachix/cachix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
|
|
| |
* ci: add no-channel check
* Update .github/workflows/no-channel.yml
Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com>
Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
By generalizing the previous merge-staging action we can support a large
number of branch pairs that need to be merged periodically.
Provide two intervals, daily and every six hours, to accomodate
different needs.
Co-Authored-By: Malte Brandy <malte.brandy@maralorn.de>
|
|
|
|
|
|
|
| |
We found that many users found it difficult to locate this document.
Github supports it in the root, see:
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors
|
|
|
|
|
|
|
| |
Automation tools should instruct their users clearly what tasks are still on the user.
Updates the bot's version to get the `pull_description` feature:
https://github.com/zeebe-io/backport-action/pull/64
|
|\
| |
| | |
direct-push action: delay to workaround eventually consistent DB
|
| | |
|
|\ \
| |/
|/| |
backport action: run only when the label starts with 'backport'
|
| | |
|
| |
| |
| |
| | |
It only works sometimes and we're unable to fix it.
|
|/
|
|
| |
require approval
|
| |
|
| |
|
|
|
|
| |
This is consistent with the other actions.
|
|
|
|
|
| |
We have this set in the other actions, it prevents the action from
running in PRs made against forks.
|
|
|
|
| |
Adds three more valid branches to the rebase action.
|
|\
| |
| | |
Add backporting action
|
| | |
|
| |
| |
| | |
Co-authored-by: zowoq <59103226+zowoq@users.noreply.github.com>
|
| |
| |
| | |
Co-authored-by: zowoq <59103226+zowoq@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| | |
If "backport <branch>" label is applied to a PR,
once the PR is merged, github-actions bot will create another PR targeting
<branch> and cherry-picking commits.
|
|/
|
|
|
| |
We have this set in the other actions, it prevents the action from
running in PRs made against forks.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
- use pull_request_target to avoid having to manually approve the action
- use nixpkgs editorconfig-checker rather than external binary
|
| |
|
|
|
|
| |
Co-authored-by: zowoq <59103226+zowoq@users.noreply.github.com>
|
|
|
| |
Co-authored-by: Alyssa Ross <hi@alyssa.is>
|
|
|
|
| |
https://github.com/NixOS/nixpkgs/issues/118661
|
| |
|
|
|
|
|
| |
opened, synchronize, reopened are the defaults for `pull_request_target`,
`edited` will trigger the label action if the PRs base branch is changed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Error if the commenter doesn't have write access or maintainers can't edit the PR branch.
- Close and comment on PR after rebase so that actions are run when it's reopened.
This doesn't happen currently as we're using the default github token which isn't allowed to trigger other actions.
- Disallow unwanted rebases.
e.g. invalid branches, redundant rebases or rebasing permanent branches onto permanent branches.
|
| |
|
| |
|
|
|
|
| |
needs an explicit NIX_PATH
|
| |
|
|
|
|
| |
started the job
|
|
|
|
| |
and sandbox
|
| |
|
|
|
|
| |
faster than doing a full clone and using git diff
|
|
|
|
|
| |
It went every minute past every 6th hour, which was too often.
Now it should go on the zeroth minute every 6th hour.
|
|
|
|
|
|
|
| |
Comment on the designated issue in case of a failure.
Whoever wants to help out resolving merge conflicts can simply follow
this issue.
|