[PR #2312] [CLOSED] feat: worklow: add permissions field #2387

Closed
opened 2026-03-01 21:55:13 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/2312
Author: @Frankkkkk
Created: 5/1/2024
Status: Closed

Base: masterHead: add-permissions


📝 Commits (1)

  • 00d43eb feat: worklow: add permissions field

📊 Changes

1 file changed (+8 additions, -6 deletions)

View changed files

📝 pkg/model/workflow.go (+8 -6)

📄 Description

The permissions field can either be a top level key, or a per-job one. It supports a map of scope<>permission relations.
For example, to allow the jobs to write to the the packages registry, the following must be set:

permissions:
  packages: write

this fixes that.
Right now, this field is not used/useful when running the actions locally, but can be used to handle permissions on forges that implement the same action format, such as Forgejo/Gitea.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/2312 **Author:** [@Frankkkkk](https://github.com/Frankkkkk) **Created:** 5/1/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `add-permissions` --- ### 📝 Commits (1) - [`00d43eb`](https://github.com/nektos/act/commit/00d43eb9fb15fda96792722622c31a40de7ac55b) feat: worklow: add `permissions` field ### 📊 Changes **1 file changed** (+8 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `pkg/model/workflow.go` (+8 -6) </details> ### 📄 Description The `permissions` field can either be a top level key, or a per-job one. It supports a map of scope<>permission relations. For example, to allow the jobs to write to the the packages registry, the following must be set: ```yaml permissions: packages: write ``` this fixes that. Right now, this field is not used/useful when running the actions locally, but can be used to handle permissions on forges that implement the same action format, such as Forgejo/Gitea. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-01 21:55:13 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#2387
No description provided.