Skip to content

Clarified the instructions in issue templates #52

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

Merged
Prev Previous commit
Next Next commit
Update issue templates to refer to "Properties File" for consistency
  • Loading branch information
SableRaf committed Jan 13, 2025
commit 52321e3d944fc88fea5aa9681fb2c29b4557c60d
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/1_new-library.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ body:
- type: markdown
attributes:
value: |
### About the `.txt` File
### About the Properties File

The `.txt` file (e.g., `myLibrary.txt`) is necessary for submitting your library. It should be a direct copy of your `library.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.
A properties file (e.g., `myLibrary.txt`) is necessary for submitting your library. It should be a direct copy of your `library.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.

**Example:**
If your release artifacts are hosted at `https://github.com/yourusername/yourrepo/releases/latest/`, ensure these files are available:
Expand Down
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/2_new-tool.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ body:
- type: markdown
attributes:
value: |
### About the `.txt` File
### About the Properties File

The `.txt` file (e.g., `myTool.txt`) is necessary for submitting your tool. It should be a direct copy of your `tool.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.
A properties file (e.g., `myTool.txt`) is necessary for submitting your tool. It should be a direct copy of your `tool.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.

**Example:**
If your release artifacts are hosted at `https://github.com/yourusername/yourrepo/releases/latest/`, ensure these files are available:
Expand Down
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/3_new-mode.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ body:
- type: markdown
attributes:
value: |
### About the `.txt` File
### About the Properties File

The `.txt` file (e.g., `myMode.txt`) is necessary for submitting your mode. It should be a direct copy of your `mode.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.
A properties file (e.g., `myMode.txt`) is necessary for submitting your mode. It should be a direct copy of your `mode.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.

**Example:**
If your release artifacts are hosted at `https://github.com/yourusername/yourrepo/releases/latest/`, ensure these files are available:
Expand Down
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/4_new-examples.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ body:
- type: markdown
attributes:
value: |
### About the `.txt` File
### About the Properties File

The `.txt` file (e.g., `myExamples.txt`) is necessary for submitting your example pack. It should be a direct copy of your `examples.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.
A properties file (e.g., `myExamples.txt`) is necessary for submitting your example pack. It should be a direct copy of your `examples.properties` file, hosted in the same directory as your `.zip` distribution, and share the same base name.

**Example:**
If your release artifacts are hosted at `https://github.com/yourusername/yourrepo/releases/latest/`, ensure these files are available:
Expand Down