Adds ability to create commits #264
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d5d2b15 to
fc32ef8
Compare
Contributor
Author
|
@NARKOZ ping |
Collaborator
|
What's with all the indentation changes in |
Contributor
Author
|
Rubymine auto format. |
Contributor
Author
|
Are the indentation changes holding this PR up? Do you need me to change this. Really need this feature added. @asedge |
Contributor
Author
|
The spacing differences are because the code is considered a continuation line which my editor spaces 4 over instead of 2. |
Collaborator
|
Yeah, please clean up those changes unrelated to the PR. Thanks! |
* the user can now create commits through the gem by posting
one or more file changes (file content). This can be extremely
useful in situations where you don't want to distribute ssh keys,
and use api tokens instead with CI systems.
Collaborator
|
@logicminds Great, thanks! |
andrew
added a commit
to librariesio/gitlab
that referenced
this pull request
Apr 11, 2017
* upstream/master: release 4.0.0 Move .file_contents to RepositoryFiles module, matching GitlabHQ API doc. Also update route so it actually works with APIv4. Fix .get_file for new APIv4 route Update gitignore Add ability to get all issues a merge_request will close (NARKOZ#271) Update CHANGELOG, add some missing entries. Block/unblock user now uses POST instead of PUT. Fixes NARKOZ#262. Adds ability to create commits (NARKOZ#264) Rename "git hook" to "push rule". Closes NARKOZ#233. Change project fork endpoint for v4 API. Closes NARKOZ#236. Add v4-endpoint to fetch all merge_requests for a milestone (NARKOZ#265) Fixes NARKOZ#222, using deploy_keys endpoint (NARKOZ#261) (Un)subscribe to issues and merge_requests (NARKOZ#260) Update merge_request endpoints to new merge_requests endpoints (NARKOZ#256) Fix failing test that was called with a pre-urlencoded string. Allow issues to use NAMESPACE/REPO identifier (NARKOZ#255) Feature/230 note that project id can also be a string (NARKOZ#253)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
one or more file changes (file content). This can be extremely
useful in situations where you don't want to distribute ssh keys,
and use api tokens instead with CI systems.