liquid-development/game-tracker
3
0
Fork 0
Code Issues 13 Pull Requests 5 Actions Releases 1 Activity

Bot-User für Workflow erstellen #53

New Issue
Open
opened 2025-11-23 00:15:33 +00:00 by flixcoo · 2 comments
flixcoo commented 2025-11-23 00:15:33 +00:00
Owner
Copy Link

Bot-User für Workflow erstellen

Für den Push-Workflow ist es notwendig einen eigenen User anzulegen um mit diesem die Pushes durchzuführen.

# Bot-User für Workflow erstellen Für den Push-Workflow ist es notwendig einen eigenen User anzulegen um mit diesem die Pushes durchzuführen.
flixcoo added this to the Minimum Viable Product (MVP) milestone 2025-11-23 00:15:33 +00:00
flixcoo added the
Task
Setup
 label 2025-11-23 00:15:33 +00:00
gelbeinhalb was assigned by flixcoo 2025-11-23 00:15:33 +00:00
flixcoo added a new dependency 2025-11-23 00:15:58 +00:00
#44 Workflows um Format Stage erweitern
gelbeinhalb commented 2025-11-23 18:58:14 +00:00
Owner
Copy Link

Hast du geguckt ob es sowas generelleres gibt, wo ich einen Bot-user hinzufügen kann, den dann alle nutzen können? Oder muss ich da pro Organisation einen adden?

Hast du geguckt ob es sowas generelleres gibt, wo ich einen Bot-user hinzufügen kann, den dann alle nutzen können? Oder muss ich da pro Organisation einen adden?
flixcoo commented 2025-11-23 19:04:22 +00:00
Author
Owner
Copy Link

Hast du geguckt ob es sowas generelleres gibt, wo ich einen Bot-user hinzufügen kann, den dann alle nutzen können? Oder muss ich da pro Organisation einen adden?

grafik.png

grafik.png

> Hast du geguckt ob es sowas generelleres gibt, wo ich einen Bot-user hinzufügen kann, den dann alle nutzen können? Oder muss ich da pro Organisation einen adden? ![grafik.png](/attachments/da72dcf1-0ab1-4f76-aac2-2b7a3251cd7e) ![grafik.png](/attachments/7a6f9c8b-a1de-4aeb-8d52-70a7dbf8be01)
grafik.png
184 KiB
grafik.png
166 KiB
flixcoo modified the milestone from Minimum Viable Product (MVP) to Alpha 2025-12-15 18:53:23 +00:00
gelbeinhalb added the
Priority
Low
4
 label 2025-12-25 01:20:58 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Duplicate
This issue or pull request already exists
Layer
BE
Issues/PRs related to the backend
Layer
DB
Issues/PRs related to the database
Layer
FE
Issues/PRs related to the frontend
Layer
Full Stack
Issues/PRs spanning multiple layers (frontend, backend, database)
PR
In Review
1
Pull Request that is reviewed
PR
Ready for Review
2
Pull Requests which are ready to be reviewed
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Task
Bug
Reports of unexpected behavior or defects in existing functionality.
Task
Documentation
Tasks related to improving or adding documentation (READMEs, code comments, guides).
Task
Enhancement
Improvements or optimizations to existing features (non-breaking changes).
Task
Feature
Requests for new functionality or significant additions to the project.
Task
Refactoring
Task
Setup
Tasks related to project configuration, tooling, or infrastructure.
Task
Testing
Issue or pull request related to testing
Workflow
Abandoned
4
Somebody has started to work on this but abandoned work
Workflow
Backlog
4
Issues/PRs that are acknowledged but not being actively worked on yet.
Workflow
In Progress
3
Issues/PRs currently being actively worked on.
Workflow
On Hold
3
Issues/PRs temporarily being paused or blocked.
Workflow
Won't Fix
5
This issue won't be fixed
No Label
Priority
Low
4
Task
Setup
Milestone
No items
No Milestone Alpha
Assignees
Clear assignees
flixcoo gelbeinhalb sneeex
No Assignees gelbeinhalb
2 Participants
Notifications
Due Date
No due date set.
Blocks
#44 Workflows um Format Stage erweitern
liquid-development/game-tracker
Reference: liquid-development/game-tracker#53
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?