Skip to content

Commit 13e9cd4

Browse files
author
Andrei Jiroh Eugenio Halili
committed
Add some content to Post-0Repo Creation Checklist
Signed-off-by: Andrei Jiroh Eugenio Halili <andreijiroh@madebythepins.tk>
1 parent cf4f5f0 commit 13e9cd4

File tree

2 files changed

+51
-1
lines changed

2 files changed

+51
-1
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: Example Mergify configurations
3+
---
4+
5+
## Automagically merge Dependabot PRs
6+
7+
```yml
8+
# Conflicts with the following PR rules, please comment them out first:
9+
# - Automate base image upgrade review process from Dependabot
10+
# - Ship Dependabot PRs when approved by humans
11+
# Remember that you MUST ALWAYS REVIEW THE CHANGELOGS
12+
# before your release it as https://github.io/cdr/code-server/releases.
13+
- name: Automagically ship Dependabot PRs
14+
conditions:
15+
- author~=^dependabot(|-preview)\[bot\]$
16+
- label=Updated by Dependabot
17+
- label=packages/docker-base-images
18+
- base=main
19+
actions:
20+
review:
21+
type: APPROVE
22+
message: |
23+
Approving and merging @dependabot's pull request, to be shipped in the following image tags: `develop`
24+
25+
Maintainers have been advised to to create an new release regarding this base image upgrade as soon as possible for patches, including security fixes, and within the next 48-72 hours for minor releases. For major releases, expect breaking changes and notify your users accordingly before creating an new GitHub release.
26+
27+
To learn more about this guideline, please read your `docs/release-management/automated-base-image-upgrades.md` or through <https://cdrs-docs.rtapp.tk/base-images-dependabot> in case your copy of maintainers' docs go outdated.
28+
29+
--
30+
31+
This PR has been merged automagically by Mergify. Read `docs/post-repo-creation/mergify.md` or visit <https://cdrs-docs.rtapp.tk/mergify> to learn more.
32+
merge:
33+
action: merge
34+
```
Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,19 @@
11
---
22
title: Post Repository Creation Checklist
3-
---
3+
---
4+
5+
After you either generated a new repo from an GitHub template or duplicated it, you need to configure encrypted secrets for GitHub Actions, update contact links, and install Mergify, among other things.
6+
7+
## TL;DR
8+
9+
Here's the gist of what you do as a new template maintainer:
10+
11+
* [Install Mergify on your account/org](https://github.com/apps/mergify/installations/new). We're working on an GitHub Action workflow if you don't prefer to use Mergify instead.
12+
* Configure encrypted secrets for Docker Hub, RHQCR (the public instance on <https://quay.io>) and GHCR
13+
* Adjust GitHub repository settings, and optionally update sponsor links.
14+
15+
## Step 1: Installing Mergify
16+
17+
**Transferring to or has repo creation permissions in `code-server-boilerplates` org?** Skip this step, since we installed that GitHub app across the org.
18+
19+
Otherwise, [install the app](https://github.com/apps/mergify/installations/new) in an account/org where your template is. If you don't want to install the app across all repos, select **Only select repositories** and manually add that repo before hitting `Install`.

0 commit comments

Comments
 (0)