Bump github/branch-deploy from 7.0.0 to 7.1.0

[dependabot]

Bumps github/branch-deploy from 7.0.0 to 7.1.0.

Release notes

Sourced from github/branch-deploy's releases.

v7.1.0

This release introduces a new input parameter for this Action:

• deploy_message_path - The path to a markdown file which is used as a template for custom deployment messages

You can read more about this change under the dedicated documentation for custom deployment messages.

This release will give users of this Action even more flexibility to customize what their projects deployment messages look like! All this can now be done in our familiar friend, markdown and it also comes with nunjucks template rendering support 🚀.

What's Changed

• File Based Post Deploy Messages by @​GrantBirki in github/branch-deploy#174
• Code cleanup by @​GrantBirki in github/branch-deploy#175
• node package updates by @​GrantBirki in github/branch-deploy#176
• Documentation Updates by @​GrantBirki in github/branch-deploy#177
• add example screenshot by @​GrantBirki in github/branch-deploy#178

Full Changelog: github/branch-deploy@v7.0.0...v7.1.0

Commits

• b7dee40 Merge pull request #178 from github/custom-comment-screenshot
• 6c527d4 add example screenshot
• d3c3eba Merge pull request #177 from github/documentation-updates
• 60f07cb add note
• 8d1fe09 add Custom Markdown File docs
• 51db5e5 update old noop_trigger value
• dab72fe fix bare url
• 37b50ea Merge pull request #176 from github/node-updates
• dd54814 node package updates
• 50e32ea Merge pull request #175 from github/code-cleanup
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

1. 👀 Observe the CI jobs and tests to ensure they are passing

2. ✔️ Obtain an approval/review on this pull request

3. 🚀 Deploy your pull request to the development environment with .deploy to development

4. 🚀 Deploy your pull request to the production environment with .deploy

   If anything goes wrong, rollback with .deploy main

5. 🎉 Merge!

Need help? Type .help as a comment or visit the usage guide for more details

Please note, if you have a more complex change, it is advised to claim a deployment lock with .lock <environment> --reason <reason> to prevent other deployments from happening while you are working on your change.

Once your PR has been merged, you can remove the lock with .unlock <environment>.

[dependabot]

Superseded by #214.