Samaya
Pre-beta. Samaya is early software: expect rough edges and changes between releases. Keep a backup of your Org files.

GitHub

The GitHub panel lists issues and pull requests from a saved search. Drag one onto a day to plan it as an Org task.

Signing in

Samaya uses the first of these it finds:

  1. A personal access token saved in Settings → GitHub. The page says Token in use, and Delete token removes it, after asking you to confirm.

  2. Your gh CLI login, from gh auth token. With gh signed in, there is nothing to set up.

A token needs read access to issues and pull requests in the repositories you want to see. For a fine-grained token, that is Issues: Read and Pull requests: Read. For a classic token, it is repo, or public_repo for public repositories only.

Filters

Each filter is a name and a query in GitHub's search syntax. The panel shows them as tabs, and Settings → GitHub adds, edits and removes them. The defaults are:

NameQuery
Assigned to meis:open assignee:@me archived:false
Review requestsis:open is:pr review-requested:@me archived:false

Use ↻ to refresh the panel. If a refresh fails, check the error and use the retry button.

Planning an item

Turn on Settings → GitHub → Show in the rail, then open the panel from the GitHub mark in the rail; it takes the place of the day calendar. Drag a card onto a day to create a task there with a 30-minute estimate, in Inbox.org; drop it on a calendar's timeline to block that half hour too. The task has the item's title, and its properties record where it came from:

* TODO Fix the crash
SCHEDULED: <2026-09-28 Mon>
:PROPERTIES:
:ID: ...
:EFFORT: 0:30
:SAMAYA_SOURCE_INTEGRATION: github
:SAMAYA_SOURCE_ITEM: ...
:SAMAYA_SOURCE_REFERENCE: acme/app#9
:END:

An item that is already planned shows ✓ Planned and cannot be dragged again. ↗ opens it on GitHub. To un-plan it, drag its task back onto the panel: the task moves to the trash and the item can be planned again.