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
..
ISSUE_TEMPLATE	modified out-of-date template	2020-10-22 11:29:39 +02:00
workflows	.github/workflows/merge-staging.yml: Include branch in comment	2021-05-13 13:58:14 +02:00
CODEOWNERS	pkgs/top-level: init expression for haskell-updates jobset	2021-05-03 11:40:03 +02:00
CONTRIBUTING.md	treewide: stdenv.lib -> lib	2021-01-24 01:49:49 +01:00
ISSUE_TEMPLATE.md	ISSUE_TEMPLATE: 'nix run' -> 'nix-shell -p'	2020-01-05 22:47:43 +01:00
labeler.yml	.github/labeler.yml: Update GNOME file patterns	2021-05-12 19:38:41 +02:00
PULL_REQUEST_TEMPLATE.md	PULL_REQUEST_TEMPLATE.md: use rendered docs	2020-11-13 16:18:19 -08:00
STALE-BOT.md	STALE-BOT.md: Mention github not notifying	2020-12-09 23:24:02 +02:00
stale.yml	stale-bot: TL;DR tweak	2020-10-26 12:58:04 -05:00