jj/.github/ISSUE_TEMPLATE.md

## Description

<!-- Thanks for your report! Please describe your problem or request here.
For questions, use https://github.com/martinvonz/jj/discussions/new instead.
Feel free to remove any of the sections below if they don't seem useful. -->


## Steps to Reproduce the Problem

1.
1.
1.

## Expected Behavior


## Actual Behavior


## Specifications

- Platform:
- Version:
github: clarify a few things in the issue template 2022-03-13 05:58:41 +00:00			`## Description`

			`<!-- Thanks for your report! Please describe your problem or request here.`
			`For questions, use https://github.com/martinvonz/jj/discussions/new instead.`
			`Feel free to remove any of the sections below if they don't seem useful. -->`


Boilerplate for new Google open source project 2020-12-12 07:37:25 +00:00			`## Steps to Reproduce the Problem`

			`1.`
			`1.`
			`1.`

github: put repro steps first in issue template I agree with @unrelentingtech's comment in #54 that the steps to reproduce should come before the expected and actual behavior. I don't know where I got the current template from. I think it was from Google's process for open-sourcing the project. I also removed the version field from the template for now since I haven't started updating it regularly yet. I should start doing that. 2022-02-27 19:54:21 +00:00			`## Expected Behavior`


			`## Actual Behavior`


Boilerplate for new Google open source project 2020-12-12 07:37:25 +00:00			`## Specifications`

releasing: add missing trailing newlines to .github/ files 2020-12-12 07:44:55 +00:00			`- Platform:`
github: include version number in issue template again Now that we have a changelog and I plan to do releases once in a while, it makes sense again to have the version number in the issue template. 2022-03-13 07:31:52 +00:00			`- Version:`