Skip to content

Add new maintainer and add release instructions #437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2020
Merged

Add new maintainer and add release instructions #437

merged 1 commit into from
Jan 25, 2020

Conversation

jcouball
Copy link
Member

Your checklist for this pull request

🚨Please review the guidelines for contributing to this repository.

  • Ensure all commits include DCO sign-off.
  • Ensure that your contributions pass unit testing.
  • Ensure that your contributions contain documentation if applicable.

Description

  • Since I am not a maintainer, add myself to MAINTAINERS.md
  • Document release instructions for future maintainers in RELEASING.md

@jcouball jcouball requested a review from perlun January 22, 2020 17:25
in this guide
* Create a new tag using [git-extras](https://github.com/tj/git-extras/blob/master/Commands.md#git-release)
`git release` command
* For example: `git release v1.6.0.pre1`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the tag really be made in the actual PR? This will work but only as long as we are strict with using --ff-only-style merging (fast forward merges without merge commits).

The other option would be to tag it once the PR is merged instead.


* Verify that you are not on a fork with the command `git remote -v`
* Verify that the version number is correct by running `rake -T` and inspecting
the output for the `release[remote]` task
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's also possible to have multiple remotes in a git working copy; this is how I typically do it both at work. But I'm not sure it plays that well with the rake release command, so feel free to keep this like it's phrased if it works best for you that way.

Add instructions for releasing the git gem
Signed-off-by: James Couball <jcouball@yahoo.com>
@jcouball jcouball merged commit 7e5bdc9 into ruby-git:master Jan 25, 2020
@jcouball jcouball deleted the update_maintainers branch January 25, 2020 16:28
AgoraSecurity pushed a commit to AgoraSecurity/ruby-git that referenced this pull request Feb 21, 2020
Add instructions for releasing the git gem
Signed-off-by: James Couball <jcouball@yahoo.com>Signed-off-by: Agora Security <github@agora-security.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants