Files
gitlabhq/doc
Douwe Maan 7e8dc22dd7 Merge branch 'merge-if-green' into 'master'
Merge when build succeeds

### What does this MR do?
Adds a button to a MR when the build/ci is running so it can be merged when/if the build is successfull.

### Are there points in the code the reviewer needs to double check?
English spelling and whether or not the grammer is correct.

### Why was this MR needed?
When you expect its all good, and don't want to revisit the current MR it can be accepted allready.

### What are the relevant issue numbers / Feature requests?
Fixes #2640 -- although `Merge if green` is replaced with `Merge when the build succeeds` the general idea is the same.

### Screenshots (if relevant)
![Screenshot_from_2015-12-07_10-34-39](/uploads/b90b558b6ad6c8266bc9c96120d86f96/Screenshot_from_2015-12-07_10-34-39.png)

![Screenshot_from_2015-11-02_17-26-56](/uploads/9f52f56e3c5e9ec63cb8f42978c92a52/Screenshot_from_2015-11-02_17-26-56.png)
![Screenshot_from_2015-11-02_17-27-03](/uploads/119fc18c9b15ff73dc38010ac5b6244a/Screenshot_from_2015-11-02_17-27-03.png)

![Screenshot_from_2015-12-03_10-08-14](/uploads/bad7b35c7d129981d43631877c958be0/Screenshot_from_2015-12-03_10-08-14.png)

![Screenshot_from_2015-11-02_17-27-16](/uploads/b616d750a16cc11ba72f2ca84213515e/Screenshot_from_2015-11-02_17-27-16.png)

### Further considerations
What if there are minor things needed solving, e.g. Rubocop, the current implementation will reset the approved status of the MR. It might be a consideration keep the approval for team member, or even guests. This would require an extra option in the Admin screen, though might add extra value.

#### TODO
- [x] Docs
- [x] Specs

/cc @DouweM @rspeicher

See merge request !1729
2015-12-09 09:37:38 +00:00
..
2015-11-25 12:27:07 +00:00
2015-12-08 22:37:07 +01:00
2015-12-08 18:25:24 +02:00

Documentation

User documentation

CI Documentation

CI Languages

CI Services

CI Examples

Administrator documentation

  • Custom git hooks Custom git hooks (on the filesystem) for when web hooks aren't enough.
  • Install Requirements, directory structures and installation from source.
  • Integration How to integrate with systems such as JIRA, Redmine, LDAP and Twitter.
  • Issue closing Customize how to close an issue from commit messages.
  • Libravatar Use Libravatar for user avatars.
  • Log system Log system.
  • Operations Keeping GitLab up and running
  • Raketasks Backups, maintenance, automatic web hook setup and the importing of projects.
  • Security Learn what you can do to further secure your GitLab instance.
  • System hooks Notifications when users, projects and keys are changed.
  • Update Update guides to upgrade your installation.
  • Welcome message Add a custom welcome message to the sign-in page.
  • Reply by email Allow users to comment on issues and merge requests by replying to notification emails.
  • Migrate GitLab CI to CE/EE Follow this guide to migrate your existing GitLab CI data to GitLab CE/EE.
  • Git LFS configuration

Contributor documentation

  • Development Explains the architecture and the guidelines for shell commands.
  • Legal Contributor license agreements.
  • Release How to make the monthly and security releases.