Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 259
    • Issues 259
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Wiki
  • Processes
  • gitlab howto

gitlab howto · Changes

Page history
Added a note about issue must have descriptions authored Dec 07, 2020 by Tomek Mrugalski's avatar Tomek Mrugalski
Show whitespace changes
Inline Side-by-side
Processes/gitlab-howto.md
View page @ 3fdfc738
...@@ -18,10 +18,12 @@ git clone git@gitlab.isc.org:isc-projects/stork.git ...@@ -18,10 +18,12 @@ git clone git@gitlab.isc.org:isc-projects/stork.git
cd stork cd stork
``` ```
# Adding an issue # Creating an issue
- If you have something new to work on, create an issue in gitlab: go to https://gitlab.isc.org/isc-projects/stork. Make sure it's not assigned to any milestone, unless you discussed this with the project manager and he is ok with adding it directly to the current milestone. We have a process to triage unassigned tickets weekly and assign them to specific milestone. - If you have something new to work on, create an issue in gitlab: go to https://gitlab.isc.org/isc-projects/stork. Make sure it's not assigned to any milestone, unless you discussed this with the project manager and he is ok with adding it directly to the current milestone. We have a process to triage unassigned tickets weekly and assign them to specific milestone.
- Issues must have descriptions. You may save seconds of your time, but others will waste much more trying to figure out what's actually there to do or why. Playing a guessing game is really a time waste. Issues that don't have a description will not be accepted in milestones, except Outstanding. No exceptions.
# Working on an issue # Working on an issue
- Once you start working on an issue, assign the issue to yourself. You should also assign Doing label. There are two ways of doing that. First, you can add the label manually when browsing an issue. Alternatively, you can go to https://gitlab.isc.org/isc-projects/stork/boards and drag and drop your issue to appropriate stage. - Once you start working on an issue, assign the issue to yourself. You should also assign Doing label. There are two ways of doing that. First, you can add the label manually when browsing an issue. Alternatively, you can go to https://gitlab.isc.org/isc-projects/stork/boards and drag and drop your issue to appropriate stage.
......
Clone repository
  • Demo
  • Ideas
  • Install Prometheus Grafana
  • Install
  • Known issues
  • Processes
    • coding guidelines
    • development environment
    • gitlab howto
  • Releases
  • Releases
    • Release notes 0.1
    • Release notes 0.10
    • Release notes 0.11
    • Release notes 0.12
    • Release notes 0.13
    • Release notes 0.14
View All Pages