When would you put your code in GitLab?
Start when you want a copy of your recorded code history outside your computer or need another person to review a change. A GitLab project holds the shared repository, the folder with its history. GitLab.com hosts it for you. GitLab Self-Managed runs on infrastructure you operate.
Choose the project’s visibility and check who already has access through its group. Sending a branch copies its recorded changes to GitLab. Unsaved or unrecorded work stays on your computer. Keep passwords and customer records out of the practice project.
What can someone check before a change is combined?
Open a merge request to show the difference between your proposed branch and the shared branch. The reviewer can see the changed lines and leave comments. GitLab documents optional approvals on Free and required approval rules on Premium and Ultimate.
Before relying on a review step, check what the actual project rules enforce. If an automated check is connected, verify what it runs before you send a branch.
What does Free limit and what should you keep separately?
GitLab.com Free limits a private top-level group to five unique users, including people given access through its projects and subgroups. Personal projects outside such a group and Self-Managed have different rules. Check storage and automated-check usage separately.
Keep a separate Git copy. GitLab’s project export can carry some project history, including merge request data, between compatible GitLab versions. The file omits items such as automation variables, job artifacts, webhooks and registry images. Recreate the required settings and confirm what came across before reconnecting services.
How can you rehearse a code review without touching an account?
Draw a pretend project with a shared branch and a branch changing one homepage heading. Use paper only.
- Keep the originalMark the heading in the shared branch and the replacement heading in the proposed branch. Draw a record of that one edit.
- Read what the reviewer getsDraw the two lines the reviewer compares. Mark who may read the project and whether approval is optional or enforced on the chosen plan.
- Plan recoveryKeep the previous heading visible on the sketch until the proposed change is accepted. If the new heading is wrong after merging, plan a new change that restores it without erasing the old record.