forgejo.dev
/
infrastructure-as-code
2
1
Fork 0
Code Issues 21 Pull Requests Releases Activity

Configure Forgejo Actions (runner) #109

New Issue
Open
opened 2024-01-30 13:01:23 +00:00 by maxkratz · 1 comment
maxkratz commented 2024-01-30 13:01:23 +00:00
Owner
Copy Link

In addition/as a follow-up to these issues

  • #108
  • #107
  • #35
    I should configure Forgejo Actions with at least one runner instance.
In addition/as a follow-up to these issues - #108 - #107 - #35 I should configure Forgejo Actions with at least one runner instance.
maxkratz added the
enhancement
bug
 labels 2024-01-30 13:01:23 +00:00
maxkratz self-assigned this 2024-01-30 13:01:23 +00:00
maxkratz commented 2024-01-31 09:40:07 +00:00
Author
Owner
Copy Link
- https://medium.com/@lokanx/how-to-build-docker-containers-using-gitea-runners-600729555e07 - https://docs.gitea.com/usage/actions/design
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels
  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
maxkratz
1 Participants
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: forgejo.dev/infrastructure-as-code#109
No description provided.
Delete Branch "%!s(<nil>)"

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?