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

[PDE-3809] chore: Small followup improvement on GitHub issue templates #625

Merged
merged 2 commits into from
Feb 22, 2023

Conversation

rnegron
Copy link
Member

@rnegron rnegron commented Feb 21, 2023

Some small tweaks after seeing how the new GitHub issue templates look. View them here: https://github.com/zapier/zapier-platform/issues/new/choose

See previous PR: #622

@@ -5,7 +5,4 @@ contact_links:
about: Please direct any questions not related to feature requests or bug reports to our support team.
- name: Zapier Community
url: https://community.zapier.com/
about: Visit our community page and search for related questions and view open discussions.
- name: Zapier Platform Security Policy
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing the Security Policy link since the page already includes a button for disclosing vulnerabilities:
image

@@ -1859,7 +1859,7 @@ <h3 id="return-types">Return Types</h3>
</div><div class="row">
<div class="row-height">
<div class="col-md-5 col-sm-12 col-height docs-primary">
<p>Each of the 3 types of function should return a certain data type for use by the platform. As of core v1.0.11, there are automated checks to let you know when you&apos;re trying to pass the wrong type back. For reference, each expects:</p>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure why these changes are here, I believe they happened during husky's pre-commit?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably because a PR was merged without running the pre-commit. But this fixes it so no worries.

@@ -1859,7 +1859,7 @@ <h3 id="return-types">Return Types</h3>
</div><div class="row">
<div class="row-height">
<div class="col-md-5 col-sm-12 col-height docs-primary">
<p>Each of the 3 types of function should return a certain data type for use by the platform. As of core v1.0.11, there are automated checks to let you know when you&apos;re trying to pass the wrong type back. For reference, each expects:</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably because a PR was merged without running the pre-commit. But this fixes it so no worries.

@rnegron rnegron merged commit e5d5b11 into main Feb 22, 2023
@rnegron rnegron deleted the PDE-3809-2 branch February 22, 2023 13:55
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