Gitea commit status is missing status id

[felinira]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Overview of the Issue

When using forgejo / gitea the commit status is missing a way to identify itself (for example for branch protection rules).

Reproduction Steps

• Get atlantis to submit a status check to gitea/forgejo
• visit the /settings/branches/edit?rule_name=main sub URL
• Find an empty line under "Status checks found in the last week for this repository" with no ID

Environment details

• Atlantis version: v0.35.1
• Deployment method: docker

Atlantis server-side config file:

ATLANTIS_GITEA_BASE_URL: "https://git.example.net"
ATLANTIS_GITEA_USER: "atlantis"
ATLANTIS_GITEA_TOKEN: "<token>"
ATLANTIS_GITEA_WEBHOOK_SECRET: "<secret>"
ATLANTIS_REPO_ALLOWLIST: "test/atlantis"

Repo atlantis.yaml file:

---
version: 3
projects:
  - name: tofu
    branch: /main/
    dir: tofu
    terraform_distribution: opentofu

Additional Context

CreateStatus seems to have a "context" field. I have not investigated this further, but it could potentially be what is missing? https://anbraten.github.io/gitea-js/interfaces/CreateStatusOption.html#context

atlantis/server/events/vcs/gitea/client.go

Lines 321 to 325 in 0684077

	newStatusOption := gitea.CreateStatusOption{
	State: giteaState,
	TargetURL: url,
	Description: description,
	}

[dosubot]

Hi @felinira! I'm Dosu and I’m helping the atlantis team.

Atlantis does not currently set the context field when creating commit statuses for Gitea/Forgejo, which is why the status check appears without an identifier in branch protection rules. The relevant code in the Gitea client only sets the state, target URL, and description fields, but omits context—even though it's required by Gitea to display a status ID for checks like branch protection. You can see this in the UpdateStatus function, where the context field is not included in the CreateStatusOption struct.

This means there's currently no way to configure the status context for Gitea in Atlantis, and adding support for this field would be needed to resolve the missing status ID issue.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}