GitHub import
What a repository gives the listing, what it does not, and how a repository stays connected.
Paste https://github.com/you/thing. The repository is read through GitHub's public API — no sign-in, no permission asked of you, public repositories only.
Repository ≠ product
A repository is where code lives; a product is what somebody uses. The importer keeps them apart: the repository becomes the Repository link and an identity Guiru remembers (so a second import of the same repository is recognised), while the homepage the repository declares becomes the product's address when there is one. Without a homepage the repository page is the address, and the owner's avatar stands in for a logo until you replace it.
- Namerepository name, humanised
- Marked *Check this* —
my-cool-toolis rarely the product's name. - Description · taglinethe repository description, or the README's first paragraph
- Marked *Check this* when it came from the README.
- Tagstopics
- up to twelve
- Screenshotsimages in the README
- badges and CI shields are skipped
- Platformsfrom release assets (`.dmg`, `.exe`, `.AppImage`, `.apk`) and topics (`cli`, `extension`)
- Marked *Check this* when nothing said
- LicenceSPDX id
- shown on the preview
- Releasesthe last five, with assets
- Kept with the import so a future release sync has somewhere to start. Not shown on the listing yet; nothing is hosted or mirrored.
Connected repositories
Listing your GitHub repositories and picking three is deferred: it needs a broader GitHub permission than sign-in asks for today, and asking for it is a decision about your account, not a feature flag. URL import covers the same ground one repository at a time.