Forgejo

The Forgejo panel lists issues and pull requests from a saved search on one Forgejo (or Gitea) instance. Drag one onto a day to plan it as an Org task. See GitHub for shared planning controls.

Settings → Forgejo → Instance is your server's address, such as https://codeberg.org. Left empty, Samaya uses your tea CLI's default login's address.

For the token, Samaya uses the first of these it finds:

An access token saved in Settings → Forgejo. Delete token removes it, after asking you to confirm.
The token of your tea login for that instance. With tea login add done, there is nothing to set up.

A token needs the read:issue and read:repository scopes. Create one under Settings → Applications on your instance.

Filters

Manage saved filters in Settings → Forgejo.

A filter's query is key=value pairs joined by &:

Parameter	Finds
`state`	`open`, `closed` or `all`; `open` by default
`type`	`issues` or `pulls`; both by default
`assigned=true`	items assigned to you
`created=true`	items you opened
`mentioned=true`	items mentioning you
`review_requested=true`	pull requests awaiting your review
`labels`	items with any of these comma-separated labels
`owner`	items in this user's or organisation's repositories
`q`	items whose text contains this

The defaults are:

Name	Query
Assigned to me	`state=open&assigned=true`
Review requests	`state=open&type=pulls&review_requested=true`
Created by me	`state=open&created=true`

Use ↻ to refresh the panel.

Planning an item

As on GitHub, a card dropped on a day becomes a task in Inbox.org, recorded as coming from Forgejo by the item's ID and reference:

* TODO Fix the crash
SCHEDULED: <2026-10-12 Mon>
:PROPERTIES:
:ID: ...
:EFFORT: 0:30
:SAMAYA_SOURCE_INTEGRATION: forgejo
:SAMAYA_SOURCE_ITEM: 42
:SAMAYA_SOURCE_REFERENCE: acme/app#9
:END:

Drag the task back onto the Forgejo panel to un-plan it.

Forgejo

Instance and sign-in

Filters

Planning an item