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

Add jira base URL to PR template for ease-of-use #8342

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

internetisaiah
Copy link
Contributor

@internetisaiah internetisaiah commented Oct 30, 2024

Why are you making this change? (required)

Figured it would be helpful to have the base link in the following part of the PR template so its easy to add the link without needing to copy+paste:

<!--
For related GitHub issues and features, add "Fixes #ISSUE_NUMBER".
For Jira tickets, add the ticket number and a link to the ticket, like: [BD-NUMBER](https://jira.braze.com/browse/BD-NUMBER).
-->

Note: this does not expose any sensitive information.

Related PRs, issues, or features (optional)

  • N/A

Feature release date (optional)

  • N/A

Contributor checklist

  • I confirm that my PR meets the following:
    • I signed the Contribution License Agreement (CLA).
    • My style and voice follows the Braze Style Guide.
    • My content contains correct spelling and grammar.
    • All links are working correctly.
    • If I renamed or moved a file or directory, I set up URL redirects for each file.
    • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
    • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

  • Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
  • Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

@internetisaiah internetisaiah self-assigned this Oct 30, 2024
@cla-bot cla-bot bot added the cla-signed label Oct 30, 2024
@internetisaiah internetisaiah marked this pull request as ready for review October 30, 2024 17:51
@josh-mccrowell-braze josh-mccrowell-braze merged commit 11778ef into develop Oct 30, 2024
5 checks passed
@josh-mccrowell-braze josh-mccrowell-braze deleted the internetisaiah-patch-5 branch October 30, 2024 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants