github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 04:25:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Send actions token with webhooks #12366

New Issue
Open
opened 2025-11-02 10:07:26 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 10:07:26 -06:00
Owner
Copy Link

Originally created by @lafriks on GitHub (Jan 21, 2024).

Feature Description

Allow to set option that if enabled would send actions tokens with webhook events.

This would allow better and more smooth integration for tools that need to access repository code etc

Screenshots

No response

Originally created by @lafriks on GitHub (Jan 21, 2024). ### Feature Description Allow to set option that if enabled would send actions tokens with webhook events. This would allow better and more smooth integration for tools that need to access repository code etc ### Screenshots _No response_
GiteaMirror added the topic/webhookstype/feature labels 2025-11-02 10:07:26 -06:00
GiteaMirror commented 2025-11-02 10:07:26 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jan 21, 2024):

Interesting proposal.

What integration are you working towards? Are there any other examples of this workflow (sending auth via webhook) that you could provide?

@techknowlogick commented on GitHub (Jan 21, 2024): Interesting proposal. What integration are you working towards? Are there any other examples of this workflow (sending auth via webhook) that you could provide?
GiteaMirror commented 2025-11-02 10:07:27 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jan 22, 2024):

Not that I'm aware of existing such examples but short lived tokens could be used in woodpecker CI for example to improve reliability (if the user has not logged in for a long time in woodpecker his token would gradually expire etc) and security (pipeline would have access only to specific repo).

There can be other use cases not only CI but also for code review automation etc not to have to create token for access to many repositories

@lafriks commented on GitHub (Jan 22, 2024): Not that I'm aware of existing such examples but short lived tokens could be used in woodpecker CI for example to improve reliability (if the user has not logged in for a long time in woodpecker his token would gradually expire etc) and security (pipeline would have access only to specific repo). There can be other use cases not only CI but also for code review automation etc not to have to create token for access to many repositories
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/webhooks type/feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12366
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?