When there is created PR from the main repo, it runs two events, push to a beach and PR, which are basically the same jobs as linear history is required... so specify target branch will run jobs on master as it is puch to master and PR accordingly...
Effectively it runs half jobs harch notification event and faster iteration dues to limited number of agent for free projects :chipmunk:
When there is created PR from the main repo, it runs two events, push to a beach and PR, which are basically the same jobs as linear history is required... so specify target branch will run jobs on master as it is puch to master and PR accordingly... Effectively it runs half jobs harch notification event and faster iteration dues to limited number of agent for free projects :chipmunk: