Skip to content

Commit 23d174c

Browse files
authored
chore: /s/Pactflow/PactFlow (#53)
1 parent b2a545c commit 23d174c

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

LICENSE

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
MIT License
22

3-
Copyright (c) 2019-2021 Pactflow
3+
Copyright (c) 2019-2021 PactFlow
44

55
Permission is hereby granted, free of charge, to any person obtaining a copy
66
of this software and associated documentation files (the "Software"), to deal

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ record_deployment: .env
7575
@"${PACT_CLI}" broker record-deployment --pacticipant ${PACTICIPANT} --version ${GIT_SHA} --environment production
7676

7777
## =====================
78-
## Pactflow set up tasks
78+
## PactFlow set up tasks
7979
## =====================
8080

8181
# This should be called once before creating the webhook

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
[![Pact Status](https://testdemo.pactflow.io/matrix/provider/pactflow-example-provider/latest/master/consumer/pactflow-example-consumer-webhookless/latest/master/badge.svg)](https://testdemo.pactflow.io/pacts/provider/pactflow-example-provider/consumer/pactflow-example-consumer-webhookless/latest/master) (master/master pact)
88

9-
This is an example of how to set up a deployment pipeline for a consumer that does not make use of Pactflow/Pact Broker webhooks. This flow is a good alternative where the use of webhooks is not possible due to firewalls.
9+
This is an example of how to set up a deployment pipeline for a consumer that does not make use of PactFlow/Pact Broker webhooks. This flow is a good alternative where the use of webhooks is not possible due to firewalls.
1010

1111
Webhooks are typically used to ensure that a recently change pact gets verified by the provider immediately, rather than waiting for a provider build to run. This workflow ensures changed pacts are verified immediately by checking out the provider codebase in the consumer's pipeline, and running the verification as part of the consumer's own tests.
1212

@@ -30,4 +30,4 @@ The Test, Can-I-Deploy and Deploy steps are identical to the flow that uses webh
3030
* Check if the current version of the consumer is compatible with the *production* version of the provider.
3131
* Deploy
3232
* Deploy application
33-
* Tag the deployed version in Pactflow as 'prod'
33+
* Tag the deployed version in PactFlow as 'prod'

0 commit comments

Comments
 (0)