You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The contract_requiring_verification_published webhook triggers a build of the provider's main branch, and any deployed versions. The "provider version selectors" (effectively, { mainBranch: true}, { deployedOrReleased: true}) are hardcoded at this stage. It would be good to allow targeting of a provider version branch (or tag) so that the "matching feature" branches workflow can be easily achieved.
Eg.
consumer makes a branch feat/x
publishes pact, main+deployed versions are verified
provider makes branch feat/x, verifies { mainBranch: true}, { matchingBranch: true } and so verifies feat/x pact
consumer makes a change to the feat/x pact
webhook should be able to trigger the feat/x branch of the provider.
Also, the provider may wish to target another branch as well as the main+deployed+released.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The contract_requiring_verification_published webhook triggers a build of the provider's main branch, and any deployed versions. The "provider version selectors" (effectively, { mainBranch: true}, { deployedOrReleased: true}) are hardcoded at this stage. It would be good to allow targeting of a provider version branch (or tag) so that the "matching feature" branches workflow can be easily achieved.
Eg.
Also, the provider may wish to target another branch as well as the main+deployed+released.
Beta Was this translation helpful? Give feedback.
All reactions