GitHub issues from your meeting notes
note1 turns action items into GitHub issues in the repository that fits, from the ones you choose, and links the issue when your team already filed it. Meeting notes on GitHub, without the copy and paste.
Matched to the issues you already have
Before creating anything, note1 searches the open issues in every repository you allowed, and those closed in the last 30 days, and judges whether one already tracks the same work.
Already tracked
If an existing issue covers the action item, note1 links it and adds a comment with the meeting quote and a link to the meeting.
Possible match
When a match is uncertain, note1 shows it as a suggestion in note1. You approve it with one click, or ignore it.
New work
Action items with no match become new issues in GitHub when auto-create is on, which is the default. With it off, they appear as "create" suggestions instead.
Choose Suggest, where matches wait for one-click approval in note1, or Auto-link, where strong matches link automatically and weaker ones become suggestions.
What lands in GitHub
A new issue carries the context from the meeting, so the person doing the work does not need to replay the call.
- 1
Title and description
The action item text becomes the issue title, and its description comes along.
- 2
Owner and quote
The owner's name, the supporting quote and who said it.
- 3
Link to the meeting
A link back to the meeting in note1, with the full transcript and summary.
Closed work flows back into note1
About once an hour, note1 checks linked issues. When one is closed in GitHub, note1 can show a "Possibly done" proposal on the action item, close the item automatically, or do nothing. Your team admin chooses which. Rejected proposals are not repeated.
Connect GitHub in three steps
- 1
Connect GitHub
A team admin opens Team, then Integrations, selects GitHub and approves access with OAuth. It is connected once for the whole team.
- 2
Pick repositories and a default
Choose the repositories note1 may use, and one default repository for the times note1 is unsure where an issue belongs.
- 3
Choose how matching works
Pick Suggest, where matches wait for one-click approval, or Auto-link, where strong matches link automatically and weaker ones become suggestions.
GitHub specifics
- You choose the repositories
- Your admin picks the repositories note1 may use, and a default. note1 files each new issue in the repository that fits the action item best. When it is unsure, it follows your setting: it leaves a suggestion where someone picks the repository with one click, or it creates the issue in the default repository. When "Create tickets for new work" is off, nothing is created automatically and new issues wait as suggestions.
- No assignee
- note1 creates GitHub issues without an assignee. The owner's name is in the issue body.
- One-way sync
- Sync goes from note1 to GitHub. Editing an action item in note1 after the issue exists does not update the issue, and closing it in note1 does not close the issue.
- When items sync
- Items sync after each meeting is processed. Manually added items sync when you save them. You can retry a single item, or use Sync all on a meeting.
Frequently Asked Questions
SupportHow do I create GitHub issues from meeting notes?
A team admin connects GitHub once with OAuth, then picks the repositories note1 may use and a default. After each meeting, note1 creates an issue for each action item with no existing match, in the repository that fits best. It sends action items, not the full meeting notes.
Can note1 work with more than one repository?
Yes. Your admin chooses the repositories note1 may use, and a default. note1 looks for existing issues in all of them and files new issues in the one that fits best. When it is unsure, your setting decides: it leaves a suggestion where someone picks the repository with one click, or it uses the default repository. The choice is a best guess. When "Create tickets for new work" is off, nothing is created automatically and new issues wait as suggestions.
Does note1 assign GitHub issues?
No. Issues are created without an assignee. The owner's name is written in the issue.
Will it create duplicates of issues we already filed?
Before creating an issue, note1 searches the open issues in every repository you allowed, and those closed in the last 30 days, and judges whether one tracks the same work. Matches are linked, with a comment, or suggested.
What does the GitHub issue contain?
The action item text as the title, its description, the owner's name, the supporting quote with the speaker, and a link to the meeting in note1.
Does closing an issue update note1?
About once an hour, note1 checks linked issues. A closed issue becomes a "Possibly done" proposal, closes the action item automatically, or does nothing, depending on your admin's setting.
More AI meeting tools from note1
Other tools note1 sends action items to, and Slack. See every note1 integration on the integrations page.
Slack
Post meeting recaps and ask note1 from Slack.
Linear
Send action items to Linear, matched to existing issues.
Jira
Send action items to Jira Cloud, matched to existing issues.
Asana
Send action items to Asana projects, matched to open tasks.
Trello
Add action items to a Trello list, matched to existing cards.
Todoist
Send action items to a Todoist project as tasks.
Motion
Send action items to a Motion workspace as tasks.
Notion
Add action items to a Notion database as pages.
Stop retyping action items into GitHub
Connect GitHub once for your team, pick where items go, and let note1 link or create issues after each meeting.