Skip to content

docs: no GitLab mirror of the template yet #8

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.

Sign up for GitHub

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
AlexeyShalaev merged 1 commit into from
Oct 7, 2026
Merged

docs: no GitLab mirror of the template yet #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/getting-started/gitlab.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ See [Set up a hub's platform](../guide/setup.md#gitlab).

1. **Create the hub.** Choose *New project → Import project → Repository by URL* and give
the URL of [the template](https://github.com/bedrock-python/engineering-assets-template),
or fork its mirror at `gitlab.com/bedrock-python/engineering-assets-template`.
`https://github.com/bedrock-python/engineering-assets-template.git`.
2. **Create two service accounts** and add them to the groups that own your
repositories. On instances without service accounts, use group access tokens. Keep
the hub out of those groups: put it in a group or subgroup the accounts don't belong
Expand Down
2 changes: 1 addition & 1 deletion docs/project/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ Once, when the template is first published:

- *Settings → General*: tick **Template repository**.
- *Settings → Actions → General*: **Disable actions**. The template's workflows are a hub's: they deliver from the default branch and check every pull request of a hub, and in the template itself, with the placeholder `id` and no keys, every run would fail (`check` rejects the placeholder by design). touchmark's own CI checks the template instead (`ci.yml`, job `template`). Dependabot's version updates still open pull requests there.
- The GitLab mirror `gitlab.com/bedrock-python/engineering-assets-template` that the template's README offers: create it, and turn **CI/CD** off in its *Settings → General → Visibility, project features, permissions*, for the same reason. Keep it in sync from outside the template: a workflow placed in the template is copied into every hub created from it.
- A GitLab mirror `gitlab.com/bedrock-python/engineering-assets-template`: create it, and turn **CI/CD** off in its *Settings → General → Visibility, project features, permissions*, for the same reason. Keep it in sync from outside the template: a workflow placed in the template is copied into every hub created from it. Offer it in the template's README and in [GitLab](../getting-started/gitlab.md) only once it exists; until then both give the template's URL on GitHub to import.

## Try a release locally

Expand Down
Loading