Skip to content

ci/update: use nix-community GitHub App (backport #3361) #3364

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

Merged
merged 1 commit into from
May 23, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 23, 2025

As discussed on matrix, use the nix-community GitHub APP setup by @zowoq, instead of @GaetanLepage's SSH Deploy Key, for work done by the update CI workflow.


This is an automatic backport of pull request #3361 done by [Mergify](https://mergify.com).

@MattSturgeon

This comment was marked as resolved.

This comment was marked as outdated.

This comment was marked as outdated.

@MattSturgeon

This comment was marked as resolved.

This comment was marked as resolved.

This comment has been minimized.

Copy link
Contributor Author

mergify bot commented May 23, 2025

This pull request, with head sha 0f874b084d04ca36d288c6f08df689390e916bbc, has been successfully merged with fast-forward by Mergify.

This pull request will be automatically closed by GitHub.

As soon as GitHub detects that the sha 0f874b084d04ca36d288c6f08df689390e916bbc is part of the nixos-24.11 branch, it will mark this pull request as merged.

It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch mergify/bp/nixos-24.11/pr-3361, this means GitHub will fail to detect the merge.

@mergify mergify bot merged commit 0f874b0 into nixos-24.11 May 23, 2025
4 checks passed
@MattSturgeon MattSturgeon deleted the mergify/bp/nixos-24.11/pr-3361 branch May 23, 2025 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants