Detect production repo / branch #29

Open
opened 2023-02-12 03:08:31 +01:00 by PeterSurda · 0 comments
Owner

There should be a step to detect the production repo and branch, so that automated deployment (another step) can be setup. Automated deployment shouldn't run for forks and PRs, for example. Maybe these will have a different deployment even, into a testing environment?

There should be a step to detect the production repo and branch, so that automated deployment (another step) can be setup. Automated deployment shouldn't run for forks and PRs, for example. Maybe these will have a different deployment even, into a testing environment?
PeterSurda self-assigned this 2023-02-12 03:08:31 +01:00
PeterSurda added the
enhancement
label 2024-05-27 04:05:18 +02:00
PeterSurda added this to the Default project project 2024-05-27 04:05:25 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
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: Bitmessage/buildbot_multibuild#29
No description provided.