Closed iteles closed 7 years ago
The first step in the process is to search through the backlog for existing issues.
But if I don't know that the backlog is managed through issues and I will be expected to raise one before starting work, will this make sense to me?
My suggestion here would be something like this to provide context:
At dwyl we use issues to log our user stories (and technical tasks) to ensure we have a single version of the truth.
My expectation is that the link in this section explains enough if people need it.
https://github.com/dwyl/contributing/commit/d7c9580fedce988e029a8587a8f7bdd39e77f3ca#diff-04c6e90faac2675aa89e2176d2eec7d8R43
Good thinking Brain! 🐭
nelsonic
commented
7 years ago
The first step in the process is to search through the backlog for existing issues.
But if I don't know that the backlog is managed through issues and I will be expected to raise one before starting work, will this make sense to me?
My suggestion here would be something like this to provide context:
My expectation is that the link in this section explains enough if people need it.
https://github.com/dwyl/contributing/commit/d7c9580fedce988e029a8587a8f7bdd39e77f3ca#diff-04c6e90faac2675aa89e2176d2eec7d8R43