Help

Forger shows the work on the TYPO3 Core in one place: the issues of Forge and the changes on Gerrit, sorted into lists that answer what needs a review?, what can be merged? and what has nobody touched for months?

Where the data comes from

Forge

The issues of the project TYPO3 Core, without subprojects, private issues and private notes.

Gerrit

The changes of Packages/TYPO3.CMS with their votes, patch sets and files.

Forger copies the data in regular imports, so a change shows up after the next one has run. Every issue and change links to its original.

Activity

Open changes and issues show how long ago they were last updated: a comment, a vote, a new patch set or a new status. Bots on Gerrit only vote on uploaded patch sets, so they do not make a change look busy.

Fresh up to 14 days
Quiet 14–60 days
Stale 60–180 days
Orphaned over 180 days
  • Merged, abandoned, resolved, closed and rejected ones have no stage, and the "Activity" filter never counts them.
  • Issues "On Hold" or "Postponed" are open, so they get a stage like any other.
Not the same as "Stale issues". The stage is about time only. The list Stale issues shows issues under review without an open change.

Reviews

The lists show open changes, the ones updated last first. Each list can be sorted and searched by subject, commit message, number, Change-Id, topic and owner. Work in progress only appears in its own list and in the search. The filter "File" finds the changes that touch a file, by its path, or any file of a folder. Votes count when a person gave them. Of the CI bot only a red build counts, as Verified -1: it keeps the change from being merged.

The size of a change tells how long its review takes, like the difficulty of a game: the lines it adds and removes together, as Gerrit counts them. The filter "Size" of the lists shows the changes of one or more sizes, "Smallest first" in their sort field puts the quick reviews on top.

Easy up to 50 lines
Normal 51–250 lines
Hard 251–1000 lines
Expert 1001–2500 lines
Nightmare 2501–10000 lines
Impossible over 10000 lines

Get involved

Get involved is the place to start if you are new to the TYPO3 Core. Its first steps, from the account to the first patch, link to the Contribution Guide. Below them it lists small changes to test, good first issues, new bugs to confirm and regressions, each with a link to all of them.

Issues

Tick "Include closed" in the search to include resolved, closed and rejected issues, or merged and abandoned changes. Admins refresh an issue or a change from its page.

Dashboard

Open issues
with those opened and closed in the last 30 days
Open Gerrit changes
mergeable, with a conflict or work in progress
Waiting over a month
ready for review, no update for 30 days

Below the figures, "What needs attention" lists the changes ready to merge, the changes that wait for a review for over a month, the open regressions, as Forge marks them with "Is Regression", and the new issues.

The statistics show the issues opened and closed per week, how long changes have been waiting, the open issues and changes over three years and what was closed per year. Each chart switches to a table.

The history is worked out from when issues and changes were created and closed, so it is close to, not exactly, what Forge and Gerrit showed back then.

My Work

Log in with your TYPO3 account to see your changes and the issues you reported or are assigned to. Forger finds them by the email address and the name of your account. Closed ones are hidden until you choose "Include closed".

Sprints

Tools

Filters and search

  • The number next to a filter value is how many results it has.
  • Values of one filter add up, different filters narrow each other down: Stale or Orphaned, and on main.
  • The "Type" filter of the review lists uses the tags in the subject, like BUGFIX, TASK, FEATURE, DOCS or !!! for a breaking change.
  • The "Marked as" filter of the issue search finds the open issues that need help most: a regression, something that worked in an earlier version, or a good first issue. A good first issue is easy or trivial in Forge, new or accepted, and nobody is assigned to it.
  • The "Tags" filter of the issue search shows the most used tags of the issues found, and the ones you selected.
  • The filters of people, "Owner" of the review lists and "Author" and "Assigned to" of the issue search, show the ten with the most results. Their search finds the others in the list while you type and filters by the one you pick.
  • The search in the header finds issues from every page.
  • A text of more than 8 words, like a pasted report, finds the issues with the most similar wording, as the duplicates do. So you can find out whether somebody already reported something.

API

The API gives the issues and changes of Forger as JSON, for scripts and tools. It is read only and needs no login. The API documentation lists the endpoints, their parameters and the fields they return, the OpenAPI document describes them for tools.

  • Data. The API has what the pages have. Forger imports Forge and Gerrit every five minutes, so a new issue or patch set shows up after the next import. The url of each issue and change leads to the original. The API never returns the email addresses Forger keeps to match people. Texts stay as their authors wrote them: a merged commit message names its reviewers with their addresses, as Git does.
  • Format. Dates are ISO 8601 in UTC, like 2026-11-20T23:40:03Z. A field without a value is null, an empty list is []. Every object has all of its fields. Other sites may call the API from the browser.
  • Lists. A list returns one page and total, the number of all items the search found. limit sets the size of a page, 25 by default and 100 at most, offset the position it starts at. The next page starts at offset + limit. Together they may not exceed 10,000: narrow the search to read further.
  • Errors. A failed request returns an object with error, a message for people: 400 for a parameter value the endpoint does not accept, 404 for an issue or change Forger does not have, 429 for too many requests.
  • Values and age. breakdown=true lists the statuses, trackers and categories the issues of a search have, with their numbers: with status=all those of all issues. The updatedOn of the first item of sort=updated&status=all tells how far the imports are.
  • Limits. An address may send 120 requests a minute. Beyond that the API answers 429, and the header Retry-After says in how many seconds it takes the next one. The headers X-RateLimit-Limit and X-RateLimit-Remaining show the limit and what is left of it. Answers may be cached for a minute, the data changes with the imports only.
  • Versions. The path holds the major version, /api/v1. Version 1 only gets new fields and parameters. A change that breaks a client gets a new path.