Open jd-campbell opened 4 weeks ago
sounds fine to me but I guess @alancleary is the main arbiter of process here so will defer to him
I don't recall being in charge of the process; I was just advocating for having a spec finalized and versioned before anything was implemented. That said, I like the process you outlined, @jd-campbell. I could make that a checklist in an issue template in the repo if people think that's a good idea.
+1 to issue templates
@alancleary Can I make the issue template -- I want to practice.
@jd-campbell go for it!
@alancleary Can I make the issue template -- I want to practice.
Just be sure to add it to the repo via a PR :wink:
Just be sure to add it to the repo via a PR 😉
says the guy who recently disavowed being in charge of process... 🙊
@alancleary --- I cannot make an issue template because I need to be a repo owner to access repo settings https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
so I have to give this task back you. Sorry.
Hmm. That's not how I've created issue templates in other repos; I've always just create a .github/ISSUE_TEMPLATE/template-name.md
file in the repo. Here's an example in the graphql-server repo: https://github.com/legumeinfo/graphql-server/blob/main/.github/ISSUE_TEMPLATE/release-checklist.md
Thanks this is a great example. I will state working on this now and send a PR to you.
I would like to request a feature to the gene-search UI and I know that Alan has specific way that spec changes need to be done. Before I do anything I wanted to ask if I am on the right track on how this is supposed to be done. Below is how I was thinking about submitting a feature request. Please tell me if I am correct or not.
Steps:
Is this right?