Update platform-gitlab.md #565
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding timeline for repo migration
voidlily
reviewed
Jun 6, 2024
_articles/platform-gitlab.md
Outdated
| @@ -58,6 +58,68 @@ Note - If `secure.login.gov` is not available, existing Personal Access Tokens | |||
| continue to function. We also have break-glass procedures if needed. | |||
| See [Runbook: GitLab Access Contingency Plan](https://gitlab.login.gov/lg/identity-devops/-/wikis/Runbook:-Gitlab-Access-When-IDP-is-Down) | |||
|
|
|||
| ## Gitlab Migration | |||
| We are in the process of moving our repos to using Gitlab as their primary source of truth. Most repos will continue to mirror back to Github, in order to allow us to maintain public visibility. Once we have migrated a Repo, merging from any branch other than Gitlab will be blocked, and all PR's will need to be submitted via Gitlab. Our current timeline for migration is below: | |||
There was a problem hiding this comment.
How does this change affect members of the public wishing to contribute PRs, such as security researchers? Members of the public don't have access to gitlab.
Do we approve on github but then mirror the PR in gitlab? Something else?
There was a problem hiding this comment.
It shouldn't. The public can still contribute a PR, but a Login.gov employee will need to manually move it over to Gitlab and Merge it there after following our MR process.
Adding Gitlab migration timetable, adding words to spellcheck ignore list that were triggering on repo names.
aduth
reviewed
Jun 6, 2024
Co-authored-by: Andrew Duthie <1779930+aduth@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding timeline for repo migration