gitea/web_src/css
Excellencedev 45809c8f54
feat: Add configurable permissions for Actions automatic tokens (#36173)
## Overview

This PR introduces granular permission controls for Gitea Actions tokens
(`GITEA_TOKEN`), aligning Gitea's security model with GitHub Actions
standards while maintaining compatibility with Gitea's unique repository
unit system.

It addresses the need for finer access control by allowing
administrators and repository owners to define default token
permissions, set maximum permission ceilings, and control
cross-repository access within organizations.

## Key Features

### 1. Granular Token Permissions

- **Standard Keyword Support**: Implements support for the
`permissions:` keyword in workflow and job YAML files (e.g., `contents:
read`, `issues: write`).
- **Permission Modes**:
- **Permissive**: Default write access for most units (backwards
compatible).
- **Restricted**: Default read-only access for `contents` and
`packages`, with no access to other units.
- ~~**Custom**: Allows defining specific default levels for each unit
type (Code, Issues, PRs, Packages, etc.).~~**EDIT removed UI was
confusing**
- **Clamping Logic**: Workflow-defined permissions are automatically
"clamped" by repository or organization-level maximum settings.
Workflows cannot escalate their own permissions beyond these limits.

### 2. Organization & Repository Settings

- **Settings UI**: Added new settings pages at both Organization and
Repository levels to manage Actions token defaults and maximums.
- **Inheritance**: Repositories can be configured to "Follow
organization-level configuration," simplifying management across large
organizations.
- **Cross-Repository Access**: Added a policy to control whether Actions
workflows can access other repositories or packages within the same
organization. This can be set to "None," "All," or restricted to a
"Selected" list of repositories.

### 3. Security Hardening

- **Fork Pull Request Protection**: Tokens for workflows triggered by
pull requests from forks are strictly enforced as read-only, regardless
of repository settings.
- ~~**Package Access**: Actions tokens can now only access packages
explicitly linked to a repository, with cross-repo access governed by
the organization's security policy.~~ **EDIT removed
https://github.com/go-gitea/gitea/pull/36173#issuecomment-3873675346**
- **Git Hook Integration**: Propagates Actions Task IDs to git hooks to
ensure that pushes performed by Actions tokens respect the specific
permissions granted at runtime.

### 4. Technical Implementation

- **Permission Persistence**: Parsed permissions are calculated at job
creation and stored in the `action_run_job` table. This ensures the
token's authority is deterministic throughout the job's lifecycle.
- **Parsing Priority**: Implemented a priority system in the YAML parser
where the broad `contents` scope is applied first, allowing granular
scopes like `code` or `releases` to override it for precise control.
- **Re-runs**: Permissions are re-evaluated during a job re-run to
incorporate any changes made to repository settings in the interim.

### How to Test

1. **Unit Tests**: Run `go test ./services/actions/...` and `go test
./models/repo/...` to verify parsing logic and permission clamping.
2. **Integration Tests**: Comprehensive tests have been added to
`tests/integration/actions_job_token_test.go` covering:
   - Permissive vs. Restricted mode behavior.
   - YAML `permissions:` keyword evaluation.
   - Organization cross-repo access policies.
- Resource access (Git, API, and Packages) under various permission
configs.
3. **Manual Verification**: 
   - Navigate to **Site/Org/Repo Settings -> Actions -> General**.
- Change "Default Token Permissions" and verify that newly triggered
workflows reflect these changes in their `GITEA_TOKEN` capabilities.
- Attempt a cross-repo API call from an Action and verify the Org policy
is enforced.

## Documentation

Added a PR in gitea's docs for this :
https://gitea.com/gitea/docs/pulls/318

## UI:

<img width="1366" height="619" alt="Screenshot 2026-01-24 174112"
src="https://github.com/user-attachments/assets/bfa29c9a-4ea5-4346-9410-16d491ef3d44"
/>

<img width="1360" height="621" alt="Screenshot 2026-01-24 174048"
src="https://github.com/user-attachments/assets/d5ec46c8-9a13-4874-a6a4-fb379936cef5"
/>

/fixes #24635
/claim #24635

---------

Signed-off-by: Excellencedev <ademiluyisuccessandexcellence@gmail.com>
Signed-off-by: ChristopherHX <christopher.homberger@web.de>
Signed-off-by: silverwind <me@silverwind.io>
Signed-off-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Zettat123 <zettat123@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-03-21 15:39:47 -07:00
..
chroma Various code view improvements (#30014) 2024-03-24 12:14:03 +00:00
codemirror Inline and lazy-load EasyMDE CSS, fix border colors (#36714) 2026-02-26 10:50:44 +00:00
editor Inline and lazy-load EasyMDE CSS, fix border colors (#36714) 2026-02-26 10:50:44 +00:00
features Inline and lazy-load EasyMDE CSS, fix border colors (#36714) 2026-02-26 10:50:44 +00:00
markup Support dark/light theme images in markdown (#36922) 2026-03-21 12:44:33 +00:00
modules feat: Add configurable permissions for Actions automatic tokens (#36173) 2026-03-21 15:39:47 -07:00
repo Fix vertical alignment of `.commit-sign-badge` children (#36570) 2026-02-11 01:01:26 +00:00
shared Refactor some trivial problems (#34959) 2025-07-05 23:19:33 +08:00
standalone Enable native dark mode for swagger-ui (#36899) 2026-03-14 09:50:23 +01:00
themes Change image transparency grid to CSS (#36711) 2026-02-25 20:20:28 +00:00
actions.css Misc CSS fixes (#34638) 2025-06-07 19:57:07 +02:00
admin.css Instance-wide (global) info banner and maintenance mode (#36571) 2026-02-26 23:16:11 +08:00
base.css feat: Add configurable permissions for Actions automatic tokens (#36173) 2026-03-21 15:39:47 -07:00
dashboard.css Refactor text utility classes to Tailwind CSS (#36703) 2026-02-22 22:56:33 +00:00
easymde.css Inline and lazy-load EasyMDE CSS, fix border colors (#36714) 2026-02-26 10:50:44 +00:00
explore.css Fix and/or comment some legacy CSS problems (#33015) 2024-12-28 11:51:38 +00:00
font_i18n.css Fix `@font-face` overrides (#24855) 2023-05-24 01:48:51 +00:00
helpers.css Replace `gt-word-break` with `tw-break-anywhere` (#31183) 2024-06-04 13:57:11 +00:00
home.css Support selecting theme on the footer (#35741) 2025-10-28 18:25:00 +08:00
index.css Migrate fomantic `search` and `modal` CSS to first-party modules (#36869) 2026-03-17 07:07:48 +01:00
install.css Fix some UI problems (install/checkbox) (#30854) 2024-05-06 06:32:05 +00:00
org.css Clean up legacy form CSS styles (#33081) 2025-01-03 04:01:19 +00:00
repo.css Fix timeline event layout overflow with long content (#36595) 2026-03-12 10:25:09 +02:00
review.css Misc CSS fixes (#35888) 2025-11-19 03:02:41 +00:00
user.css Fix overflow in notifications list (#35446) 2025-09-10 13:05:35 +00:00