Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 450
    • Issues 450
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 75
    • Merge Requests 75
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Wiki
    • Processes
  • smaller edits on gitlab

Last edited by Tomek Mrugalski Nov 12, 2020
Page history

smaller edits on gitlab

This page explains how to do smaller edits. It's simpler than checking out the whole source tree. This simplified method is mostly useful for smaller changes that you don't need to test, such as documentation, changelog corrections, maybe some rewording.

If you want the full process, see gitlab howto.

  1. Create new issue and describe what the goal of the change is. You can create it here
  2. Since you're working on it, assign the ticket to yourself. It's a good practice to also add "Doing" label, so it shows on the tracking in the right place.
  3. Open the new issue and create a Merge Request. If you don't care about the branch name, just click the green "create merge request" button. If you do care, you can click the little green triangle and then use a shorter branch name, but please make sure it starts with the ticket number. E.g. instead of 1536-diverse-textual-corrections-to-the-arm you may want to use a simpler 1536-doc-update.
  4. The MR will be automatically associated with the issue. Once you click it, there's a Request to merge 1536-doc-update link. Click on it and you'll be then seeing the branch. You can make your edits there.
  5. Once you do your changes, go ahead and review your MR. It should show your changes.
  6. Once you're happy and feel that it's ready, unassign yourself, remove the "Doing" label and add "Review" label.
  7. Normal review process follows. Make sure you look at the pipeline status. We have many automated checks that can point out common mistakes.
Clone repository
  • Home
  • Hooks available
  • Processes
    • coding guidelines
    • gitlab howto
    • release process
    • smaller edits on gitlab
  • Release Notes
  • Simplified Flow Diagram
  • community developed tools
  • designs
    • Backend Assisted Lease Selection design
    • Basic LeaseQuery Design
    • Design documents
    • HA+MT Design for Multi threaded Http HA traffic
    • HA connection with MT support
    • HA split brain issues
View All Pages