[Slackbuilds-users] Updates - 20240106.1

[Bru Barwal]

On Tue, Jan 09, 2024 at 12:24:46PM -0500, Jeremy Hansen wrote:
> On Tue, Jan 9, 2024, 9:26???AM Petar Petrov <slackalaxy at gmail.com> wrote:
> 
> > >And then on github I simply make a pull request
> > how do you "simply make a pull request"?
> >
> > -p
> >
> 
> I'm a relative git and GitHub newb, but here's what I did to start working
> with GitHub. (For those who are far more knowledgeable than me, if there
> are improvements to be made, please let me know.) I'm sure GitLab is
> similar, but they have slight variations in terminology.
> 
> This is aimed at other git/GitHub newbs... if you aren't one, I apologize.

Thanks for sharing. As another newb, I found this very helpful!
 
> 1. Create a new branch for the package you're updating and switch to that
> branch. Typically this will be the package name that you're updating, but
> naming schemes are more for you than anything. The name of the branch won't
> affect the SBo admins reviewing your pull request.
>   git checkout -B $branch_name
> 2. Make the changes to the files and verify everything works. This may
> require moving those files to a clean VM to verify they build properly in a
> clean environment.

This is where I had to `git add` the changed files

> 3. Commit those changes to that branch on your local repo:
>   git commit -m "network/discord: Update version to 1.2.3"
> location/to/changes
> (If there are multiple package changes due to dependency bumps or similar,
> do an individual commit for each package.)


-- 
Matt Egger
bru.barwal at sdf.org