Skip to content

Creating an issue

Brian R. Bondy edited this page Sep 14, 2018 · 2 revisions
  • An issue should exist for every change and every pull request.
  • Issues should usually follow the issue template.
  • Issues must be actionable. If a developer cannot read it and take action on it, then the issue is likely too vague and needs some higher level planning before going into GitHub.
You can’t perform that action at this time.