Is this your first time using Github issues? Mine, too.

Sure, in the past, I’ve opened issues, mostly when I found something buggy in someone else’s repo.

This time, however, the repo is mine. Well, kinda; I’m working on a project with a buddy, so it’s really our repo. Actually, he’s written 90% of the code so far, so it’s probably his repo until I start adding a bunch of print statements to juice the numbers in my favor :)

Anyway, point being: I’ve never used Github issues in any sort of project management-y sort of way.

This is the first time. Let’s see how it works.

📝 tldr: you can link everything on Github

if you make a commit, write the issue number in that commit

now, your commit points to the issue (commit ➡️ issue)

if you make a comment, reference a commit or another issue (if applicable)

now, all these things are linked (issue ➡️ commit + issue ➡️ issue)

if you want to link issues, creat a milestone.

now you can view related issues together.

At work, I use Jira and BitBucket together.

After a first date w/ Github (this time from the repo owner’s perspective), can conceive of the site’s built-in management being enough to guide a project.

To be continued.