bulma/.github/PULL_REQUEST_TEMPLATE.md

<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->
<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->

<!-- Choose one of the following: -->
This is a **new feature | improvement | bugfix | documentation fix**.
<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->
<!-- Improvement? Explain how and why. -->
<!-- Bugfix? Reference that issue as well. -->

### Proposed solution

<!-- Which specific problem does this PR solve and how?  -->
<!-- If it fixes a particular Issue, add "Fixes #ISSUE_NUMBER" in your title -->

### Tradeoffs

<!-- What are the drawbacks of this solution? Are there alternative ones? -->
<!-- Think of performance, build time, usability, complexity, coupling…) -->

### Testing Done

None.

<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->
<!-- 1. Pull the latest `main` branch -->
<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/main/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->
<!-- 3. Make sure your PR only affects `.sass` or documentation files -->
<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/main/.github/CONTRIBUTING.md#try-your-changes). -->

<!-- How have you confirmed this feature works? -->
<!-- Please explain more than "Yes". -->

### Changelog updated?

No.

<!-- Thanks! -->
Update templates 2017-01-15 21:14:27 +00:00			`<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->`
Fix #568 2017-03-26 16:27:15 +00:00			`<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->`
Add gitter, Fix templates 2016-04-16 20:50:48 +00:00
Fix #1236 2017-10-07 15:57:19 +00:00			`<!-- Choose one of the following: -->`
			`This is a new feature \| improvement \| bugfix \| documentation fix.`
			`<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->`
			`<!-- Improvement? Explain how and why. -->`
			`<!-- Bugfix? Reference that issue as well. -->`

Update templates 2017-01-15 21:14:27 +00:00			`### Proposed solution`
Update changelog 2019-05-17 10:24:20 +00:00
Update templates 2017-01-15 21:14:27 +00:00			`<!-- Which specific problem does this PR solve and how? -->`
			`<!-- If it fixes a particular Issue, add "Fixes #ISSUE_NUMBER" in your title -->`
Add gitter, Fix templates 2016-04-16 20:50:48 +00:00
Update templates 2017-01-15 21:14:27 +00:00			`### Tradeoffs`
Update changelog 2019-05-17 10:24:20 +00:00
Update templates 2017-01-15 21:14:27 +00:00			`<!-- What are the drawbacks of this solution? Are there alternative ones? -->`
			`<!-- Think of performance, build time, usability, complexity, coupling…) -->`
Add gitter, Fix templates 2016-04-16 20:50:48 +00:00
Update templates 2017-01-15 21:14:27 +00:00			`### Testing Done`
Add gitter, Fix templates 2016-04-16 20:50:48 +00:00
Update changelog 2019-05-17 10:24:20 +00:00			`None.`

Update templates 2017-01-15 21:14:27 +00:00			`<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->`
Update various references from master to main brach 2024-10-30 15:13:17 +00:00			<!-- 1. Pull the latest `main` branch -->
			`<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/main/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->`
Document how to try the changes (#1920) * Document how to try the changes Add to the contributing guide how to rebuild the css and where the documentation to try the documentation changes is. * Remove Bulma dependencies installation form PR template Install Bulma dependencies is not needed to send a PR. * Add how to try your changes to PR templates And after that ask if you tried the changes. 2018-06-05 23:45:21 +00:00			<!-- 3. Make sure your PR only affects `.sass` or documentation files -->
Update various references from master to main brach 2024-10-30 15:13:17 +00:00			`<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/main/.github/CONTRIBUTING.md#try-your-changes). -->`
Document how to try the changes (#1920) * Document how to try the changes Add to the contributing guide how to rebuild the css and where the documentation to try the documentation changes is. * Remove Bulma dependencies installation form PR template Install Bulma dependencies is not needed to send a PR. * Add how to try your changes to PR templates And after that ask if you tried the changes. 2018-06-05 23:45:21 +00:00
			`<!-- How have you confirmed this feature works? -->`
			`<!-- Please explain more than "Yes". -->`
Fix #1236 2017-10-07 15:57:19 +00:00
Update PR template 2019-05-17 10:08:15 +00:00			`### Changelog updated?`

Update changelog 2019-05-17 10:24:20 +00:00			`No.`
Update PR template 2019-05-17 10:08:15 +00:00
Fix #1236 2017-10-07 15:57:19 +00:00			`<!-- Thanks! -->`