Skip to main content
If your team tracks work in GitHub Issues, Waterline supports that out of the box. Because GitHub Issues live alongside your code, no additional OAuth is needed — Waterline uses your existing GitHub connection.

​
Enable GitHub Issues

  1. Make sure you have a GitHub repository connected (see GitHub integration)
  2. Go to Settings → Integrations → GitHub Issues
  3. Toggle Enable GitHub Issues on
That’s it. GitHub Issues is now available as a source when you run an analysis.

​
Analyzing an issue

Go to Analyze, select GitHub Issues as the source, and enter an issue number:
Waterline fetches the issue, extracts acceptance criteria from the body, and runs the same analysis pipeline — returning a progress percentage, per-criterion breakdown, and code evidence.

​
How it compares to Jira

GitHub Issues tends to have less structured acceptance criteria than Jira. Waterline handles free-form Markdown well — checkboxes, bullet lists, and prose descriptions all work.

​
Tips for better results

  • Use task lists: - [ ] user can log in. Waterline treats each item as a candidate criterion.
  • Be specific: “password reset email sent within 30 seconds” gives clearer signals than “reset flow works”.
See Acceptance Criteria for a full guide.