Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !2179

Closed
Created Dec 05, 2012 by Administrator@rootOwner
  • Report abuse
Report abuse

Expose to API: merge_request.state, merge_request.commits

  • Overview 3
  • Commits 1
  • Changes 2

Created by: doublerebel

This exposes merge requests commits and state to the API, so that the merge-request tool Pulley-GitLab can be used to make pretty merge commits. Here is an example of a commit made with Pulley.

I have modified John Resig's original Pulley for Github to make it compatible with these GitLab API changes. I have published Pulley-GitLab to npm, so feel free to try it out.

One of the features of Pulley/Pulley-Gitlab is supporting other Issue Trackers, a feature I desire and use. Here is my working pulley-gitlab.json as example:

{
    "interactive": false,
    "remote": "gitlab",
    "server": "http://gitlab.myhost.com",
    "repos": {
        "repo_name": "http://redmine.myhost.com/redmine/doublerebel/issues/"
    }
}

Note that unlike Pulley, Pulley-GitLab looks for its config file in the current project directory, rather in the node_modules install directory.

GitLab has been very helpful for my work, so I hope this helps others. I'm much more experienced with JS than Ruby, perhaps it would be best for someone more familiar with the project to write the appropriate tests for these minor changes.

Thanks!

Charles

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/doublerebel/merge_request_commits_for_pulley