Skip to content
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

Extend git commands #50

Open
wants to merge 24 commits into
base: master
Choose a base branch
from
Open

Conversation

charlesreffett
Copy link

@charlesreffett charlesreffett commented Nov 12, 2023

This will help with the steps defined in our team's project release guide, I believe Iceman also uses a similar process. The goal is to reduce the manual steps needed to make a release.

This PR includes scripts for creating a bin directory in the user's home directory and adding it to the $PATH if it doesn't exist, as well as a script to symlink git- scripts to the bin dir.

The two git scripts extend the git command to add tickets and make-release. The former gets the new tickets from the first branch that are not in the second branch. The make-release will create a new branch and prepend the ticket information in the CHANGELOG.md.

This creates a bin/ directory in the user's home directory and puts it in the path
this ensures the home dir has a bin dir and is in the path, then symlinks the git commands
This command is used to get the new tickets between two branches
This command automates the process of preparing a new software release. It creates a release branch from the current branch, increments the version number, updates the `CHANGELOG.md`
@iBotPeaches
Copy link
Member

This looks sweet. Will test it out on some projects.

joeladam518
joeladam518 previously approved these changes Nov 13, 2023
@erik-perri
Copy link
Member

I wonder if we should move git-make-release and git-tickets into the bin folder like hop. We encouraged people to put the bin folder of this project into their path when using hop in the hope it would make things easy to update if bugs were found or new commands were added. It seems like we could get the same benefit by moving these there and just having one path for setting it up.

@charlesreffett
Copy link
Author

I wonder if we should move git-make-release and git-tickets into the bin folder like hop. We encouraged people to put the bin folder of this project into their path when using hop in the hope it would make things easy to update if bugs were found or new commands were added. It seems like we could get the same benefit by moving these there and just having one path for setting it up.

Sure, I had a similar thought and if that's something that's already handled in setting up this repo that makes it infinitely easier :)

rbondoc96
rbondoc96 previously approved these changes Jan 17, 2024
@charlesreffett
Copy link
Author

I wonder if we should move git-make-release and git-tickets into the bin folder like hop. We encouraged people to put the bin folder of this project into their path when using hop in the hope it would make things easy to update if bugs were found or new commands were added. It seems like we could get the same benefit by moving these there and just having one path for setting it up.

Moved the scripts into the project's bin dir, adding that to the path should work

@charlesreffett
Copy link
Author

I wouldn't mind this grabbing the ticket summary/title from Jira if anyone has an idea of how we could do that


## Hop

MISSING DESCRIPTION
Copy link
Member

Choose a reason for hiding this comment

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

This is what shows when you run the command, not sure if someone wants to write a more details description here.

A script that makes it easy to hop into your project containers and run commands.

README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@charlesreffett
Copy link
Author

I wouldn't mind this grabbing the ticket summary/title from Jira if anyone has an idea of how we could do that

Discussed in our team meet, if projects squash merged it would put the PR title at the top, we could use that as the default value for the ticket description in the changelog

Co-authored-by: Erik Perri <46399654+erik-perri@users.noreply.github.com>
@iBotPeaches
Copy link
Member

Guess my readme changes in Mailpit PR had some negative downsides here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants