Feb 2015 - Merge Requests

Continuing the discussion from Community Weekend February 2015:

If you need help setting up your development environment, check out the GitLab Development Kit

Adding new features:

If you want to help by adding new features to gitlab, but are not sure where to start, please take a look at our feedback forum.
There are two interesting status here. “Accepting merge requests” and “started

When you have decided that you want to work on a feature during the community weekend,
please follow these steps:

  1. Make sure no one else is currently working on it by checking the comments of the thread
  2. Make sure the feature is not already implemented in the current version of GitLab (If that is the case, please make a comment in the thread so we can close it later)

This Feature has already been implemented in the current version of gitlab. This thread can be marked as completed. #community-weekend-feb-2015

  1. Post a comment that you want to work on this feature

As part of the GitLab Community Weekend February 2015 I will attempt create a merge request for this suggestion. #community-weekend-feb-2015

  1. After you’ve done some work on it, post either a link to the finished merge request, or a link to the repository in which you’re working on the feature

  2. Make sure your merge requests follows our merge request guidelines.

Fixing bugs:

Find a reported issue in the issue tracker. If you think you can provide a fix, please follow these steps:

  1. Post a comment that you want to work on this issue

As part of the GitLab Community Weekend February 2015 I will attempt fix this issue. #community-weekend-feb-2015

  1. Write code to fix the bug

  2. Write any necessary tests to prevent this bug from happening in the future

  3. Submit a merge requests with the changes. Be sure the description references the issue.

  4. Make sure your merge requests follows our merge request guidelines.

If you are new to GitLab development (or web development in general), another alternative is to search for the label easyfix (gitlab.com, github).
Those are issues that are easy to fix, marked by the GitLab core-team. If you are unsure how to proceed but want to help, mention one of the core-team members to give you a hint, or drop by in the Freenode #gitlab IRC channel.

This topic is now unlisted. It will no longer be displayed in any topic lists. The only way to access this topic is via direct link.

This topic is now listed. It will be displayed in topic lists.