c3lf/c3lf-system-3
9
0
Fork 0
Code Issues 55 Pull requests Projects 2 Releases Wiki Activity Actions

setup automatic testing in forgejo actions #75

New issue
Closed
opened 2024-11-05 23:32:50 +00:00 by j3d1 · 0 comments
j3d1 commented 2024-11-05 23:32:50 +00:00
Owner
Copy link
No description provided.
j3d1 added this to the Ops project 2024-11-05 23:32:50 +00:00
lagertonne added reference lagertonne/test-every-time 2024-11-12 16:09:33 +00:00
j3d1 closed this issue 2024-11-13 18:15:43 +00:00
j3d1 added this to the 38C3-FeatureFreeze milestone 2024-12-24 16:08:46 +00:00
Sign in to join this conversation.
lagertonne/test-every-time
Branches Tags
Clear current reference
testing
clarity/interactive-shipment
jedi/test_new_nodejs
live
bton/tags
jedi/search
testing_stashed_1
jedi/more_tests
wip/docker_with_mail
wip/team_notifications
jedi/autodeploy_to_prod
jedi/forgejo-actions
wip/integration_testing
jedi/item_history_frontend
system2/frontend
system2/backend
system1
Clear current reference
No results found.
Labels
Clear labels   
help wanted

   
question

   
Subsystem/Backend

   
Subsystem/Frontend

   
Subsystem/Mail
  
Kind
Breaking
Breaking change that won't be backward compatible

  
Kind
Bug
Something is not working

  
Kind
Documentation
Documentation changes

  
Kind
Enhancement
Improve existing functionality

  
Kind
Feature
New functionality

  
Kind
Security
This is security issue

  
Kind
Testing
Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
help wanted
question
Subsystem/Backend
Subsystem/Frontend
Subsystem/Mail
Kind
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
38C3-FeatureFreeze
Projects
Clear projects
No items
No project
Ops
Assignees
Clear assignees
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: c3lf/c3lf-system-3#75
No description provided.
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?