Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bids_lossless_eeg bids_lossless_eeg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • bucanl_pipelines
  • bids_lossless_eegbids_lossless_eeg
  • Wiki
  • developer workflow

Last edited by Tyler Collins Apr 17, 2018
Page history

developer workflow

Developer Workflow

  1. The master branch should be considered a stable working version of the pipeline.
  2. All development should be made on the dev branch.
  3. The development branch itself should not be pushed to and instead should be pulled into.
  4. Development for features, or style should be made to a new branch based off the development branch then pushed to a branch upstream.
    • You may make pull requests to master for bug fixes that you replicate in dev
  5. The branch upstream should then be pulled through the web interface using a pull request.
    • You should squash your commits into one commit
  6. Once thoroughly tested, the development branch should be pulled into master.

For example

  1. git checkout dev
  2. git checkout -b <your name>-<your feature name>
  3. Do development here.
  4. git push origin <your branch name>
  5. From the web interface submit a pull request to the development branch
Clone repository
  • assumptions
  • bidsifying
  • configuring context config
  • configuring remote
  • contributing
  • developer workflow
  • directories
  • essinit
  • Home
  • init scripts
  • install download
  • opening eeglab
  • pipeline scripts
  • postprocessingscript
  • qc init
View All Pages