Closed SheepReaper closed 5 years ago
I haven't made any additional modifications since last week, however, I did fork the repo and merge this request into my master just so that we could see the issue templates in action. Take a peek here: https://github.com/bryan5989/jhalfs/issues/new/choose (You normally get to this page by hitting the new issue button) GitHub issue templates are weird, they have a yaml header to tell GitHub some metadata but the actual template text is markdown. (and the bug and pull templates have to have specific names, but all others can be whatever names) Hopefully this illustrates how the template translates into the form the user fills. @pierre-labastie @jhuntwork
OK, I understand now: once the files are in master, they'll appear each time you open an issue, but without the headers (containing name:, etc). That seems OK to me. I still think that "observed behavior" should be added after "steps to reproduce". But depending on the bug, I agree that there is not always a clear separation between the steps and the observation...
I've finished making all the edits I think needed making, and work with the automation and notifications. I think this is ready to squash + merge.
Seems OK to me. Can you do the squash + merge? (we'll have to discuss our policy about who's supposed to merge to master)...
Closes #5
Adds the following issue templates:
Additional items to complete: