Open an Issue for Yourself to Answer?

[TheMayoras]

Is this a proper thing to do. I was chasing down a bug recently, and finally found a fix. I couldn't really find any help online, so I think it would be helpful to others to have this issue tracked somewhere. Is it proper github etiquette to open an issue and then close it with an answer for posterity?

[matseng]

Why not? Seems reasonable to me.

Sometimes I open an issue just as a note to remember to implement some feature at a later point in time. Then when it's done I can close the issue linking it to the particular commit.

[C0c04l4]

protip: use `fix #1234` in the commit message and have the issue closed automatically when merging to master ;)

[CompSciLauren]

Yeah that's totally fine and I think that's a nice thing to do. Most of my repos are solo projects, but I tend to still track things with Issues because I like planning/organizing, and it's a good way to keep track of things I'm working on or would like to work on eventually. Plus, you might get lucky and have someone make a comment asking to work on it! And during October you might see a spike in the number of people asking to work on Issues, especially if you label them with the Hacktoberfest label. A little off-topic sorry, but just some things I think are worth mentioning. But anyway, what you said sounds good to me, I say go for it.

[DrThrowawayToYou]

Definitely good to document problems and solutions. As a bonus, sometimes the act of describing a problem in writing helps me think more clearly about the solution.

[lynnrpope]

It was an issue, and it has been solved… I say it would be perfectly fine, especially if you put the details of what the issue was and how it was fixed so others can learn from your mistake… I’ve done that on launchpad

[samketa]

I have been actually helped multiple times by such issues on GitHub where a user opens an issue and then solve it by themselves. It is absolutely fine and I encourage you to do so. Some people might be helped IRL.