| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Bumps [technote-space/get-diff-action](https://github.com/technote-space/get-diff-action) from v2.0.2 to v2.0.3.
- [Release notes](https://github.com/technote-space/get-diff-action/releases)
- [Changelog](https://github.com/technote-space/get-diff-action/blob/master/.releasegarc)
- [Commits](https://github.com/technote-space/get-diff-action/compare/v2.0.2...b1acdd3017ce344029e1ae6d2b7769c3758799fe)
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 256dbf698028f7c0fe2f7907cd3c4fcc3401af22.
This did not solve the github action failures
|
|
|
|
|
|
|
| |
We are currently seeing a lot of misterious github actions failures.
They might be linked to our github actions:
https://github.com/nixos/nixpkgs/actions
|
|
|
|
|
|
|
|
| |
Bumps [technote-space/get-diff-action](https://github.com/technote-space/get-diff-action) from v1.2.8 to v2.0.2.
- [Release notes](https://github.com/technote-space/get-diff-action/releases)
- [Changelog](https://github.com/technote-space/get-diff-action/blob/master/.releasegarc)
- [Commits](https://github.com/technote-space/get-diff-action/compare/v1.2.8...8641dcd991ed365c2647f8ee3f31c39bc03f5312)
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| | |
dependabot: automatically update github actions
|
| | |
|
|/
|
|
|
|
| |
(#88608)"
This reverts commit 1ccf44204bb15d6e4fd6155a971e3a6fbf95e8ac.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In case ofborg is down this will not mark the CI as green.
Also if other github actions are used and pass
checks will be still marked as pending even if other other github
actions have passed.
|
| |
|
|
|
|
|
|
|
|
|
| |
As somewhat discussed at: https://git.io/JJkRa, make the bot's message a
bit more instructive, and clearer as for what it will and won't do, so
random contributors will have a better idea what this is about.
Also: Split stale issues' and PRs' messages because each should
suggest different actions to do.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this, the message being written is:
```
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
1. Search for maintainers and people that previously touched the
related code and @ mention them in a comment.
2. Ask on the [NixOS Discourse](https://discourse.nixos.org/). 3. Ask on the [#nixos channel](irc://irc.freenode.net/#nixos) on
[irc.freenode.net](https://freenode.net).
```
Co-authored-by: zowoq <59103226+zowoq@users.noreply.github.com>
.github/stale.yml: fix newlines
|
| |
|
|
|
|
|
| |
We cannot run this check now, as it marks CI as green even though ofborg has not
evaluated it yet. In future we might be able to mark ofborg as a required test:
https://github.com/NixOS/nixpkgs/pull/87853#issuecomment-632676824
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
tarballs.nixos.org is omitted from the change because urls from there
are always hashed and checked
|
| |
|
| |
|
|\
| |
| | |
PHP maintainer team
|
| | |
|
|\ \
| | |
| | | |
PULL_REQUEST_TEMPLATE: try to simplify call-for-review
|
| | |
| | |
| | |
| | |
| | |
| | | |
The text is quite long and hard to read in hub (because it is one whole line
with no line breaks). Also simplified the language/sentence structure a bit for
non-native speakers.
|
|\ \ \
| |/ /
|/| | |
|