Teams where the work is tracked in GitHub and the people who need to know about it — support, account management, whoever answers the customer — do not live there.
Pull GitHub into RowFold tables you own — filter them, report on them, link them to everything else in the workspace.
And it stays current: importing again updates the same tables, adding new records and updating changed ones, so links from your other tables hold. Keep in sync does that for you hourly or daily.
Automation steps that act on GitHub when something happens in RowFold:
What it doesn't do: It has no say in what a booking page offers. An import only reads: nothing is written back to GitHub, a record deleted there stays here, and a sync runs hourly at most rather than the moment something changes. Anything else you have read about GitHub and RowFold, this page is the authority: it is generated from the connector's own code.
One repository produces two tables rather than one, because an issue and a pull request are different things people ask different questions about. Both come across whether open or closed, which is what makes any question about duration answerable.
You'll know it worked: Compare each table's row count against the repository with the state filter cleared, since both open and closed items are imported. A count that matches only the open ones means you were comparing against GitHub's default view rather than the whole set.
The valuable version files the issue and then puts the link back on the ticket, so support can answer the customer later without searching GitHub for whichever issue it became.
You'll know it worked: Trigger it on a test ticket and check three things: the issue is on the right repository, its title reads on its own, and the ticket's Issue link now opens that issue. The third is the one people forget.
An issue knows nothing about who reported it commercially. Four customers hit the same bug and that fact lives in four support threads, so nobody can say what fixing it is worth or who to tell when it ships.
Link issues to the tickets and accounts that raised them. Then the release note's distribution list is a query rather than an archaeology exercise.
Anything you want to measure about pull requests means a script. How long review takes, which repositories are slowest, whether the backlog is growing: all of it is a CSV export and a spreadsheet nobody rebuilds twice.
Issues and pull requests arrive as separate tables, so the questions are ordinary filters and saved reports rather than a maintained script.
People without a seat, or without the appetite, cannot look. So the question usually goes to an engineer, who context-switches to answer something the data already knows.
Imported rows are governed by RowFold's own permissions, so anybody can be given read access without a GitHub seat and without the ability to change anything.
Because an issue and a pull request are different things, and almost every question you would ask is about one or the other. Review duration is a pull request question; time to fix is an issue question. Putting them in one table would mean every filter starting by separating them again, and a rollup that counted both would answer something nobody asked.
No, and the import reports that rather than leaving you to notice. Issue and pull request records only; the discussion threads and review comments stay in GitHub. That is deliberate — the conversation is where engineers work, and copying it produces two half-threads. What comes across is the state everybody else needs: who, what, when, and whether it is done.
Organisation repositories need the organisation permission granted at sign-in, and some organisations additionally require an administrator to approve third-party access before anything owned by them is visible. Without it the import genuinely finds nothing under the organisation, which reads as an empty account rather than as a permission that was never granted.
Because GitHub's classic OAuth scopes are coarse: the only one that can read issues on a private repository also grants write. The narrower alternative covers public repositories only, which would break the feature for anybody whose work is private. It is the least-privilege option available for the job rather than a convenience, and nothing in the connector writes to a repository beyond opening an issue you asked it to.
It can, an hour behind at best. Importing again updates both tables, matched on the issue or pull request number, and Keep in sync does that hourly or daily; nothing is written back to GitHub by it. Each run reads the 2,000 most recently updated issues and the same number of pull requests, so on a busy repository an item left untouched long enough stops being refreshed, though it stays in the table. Anybody who needs the state to the minute should be looking at GitHub.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.