Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: WireMock Pact #281

Merged
merged 1 commit into from
May 22, 2024
Merged

docs: WireMock Pact #281

merged 1 commit into from
May 22, 2024

Conversation

tomasbjerre
Copy link
Contributor

@tomasbjerre tomasbjerre commented Apr 28, 2024

I asked, in the Slack channel, to get this tool moved to WireMock organization here on GitHub:
https://wiremock-community.slack.com/archives/C04HHJ7F20G/p1714142475488639

Will need to change the Github link in these docs if it gets moved.

I pretty much just copied my README into this file.

References

Submitter checklist

  • The PR request is well described and justified, including the body and the references
  • The PR title represents the desired changelog entry
  • If the change against WireMock 2 functionality (incompatible with WireMock 3),
    it is submitted against the 2.x branch
  • The repository's code style is followed (see the contributing guide)

Details: Contributor Guide

@tomasbjerre tomasbjerre force-pushed the feature/pact branch 2 times, most recently from cbafcb1 to 90f3857 Compare April 28, 2024 18:15
@leeturner leeturner merged commit 1f943be into wiremock:main May 22, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants