I have an issue with my Gitea Actions workflow, because at the moment I cannot test things without triggering the pipeline which deploys the change to production.
I'm using a lock file .dev-lock to prevent the pipeline to merge into the main branch, but now I want to create a separate pipeline for testing. This way I could test new feature or fix in a dedicated branch.
I have an issue with my Gitea Actions workflow, because at the moment I cannot test things without triggering the pipeline which deploys the change to production.
I'm using a lock file `.dev-lock` to prevent the pipeline to merge into the `main` branch, but now I want to create a separate pipeline for testing. This way I could test new feature or fix in a dedicated branch.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have an issue with my Gitea Actions workflow, because at the moment I cannot test things without triggering the pipeline which deploys the change to production.
I'm using a lock file
.dev-lockto prevent the pipeline to merge into themainbranch, but now I want to create a separate pipeline for testing. This way I could test new feature or fix in a dedicated branch.Closed with #10