mirror of
https://github.com/librekeys/picoforge.git
synced 2026-07-28 08:01:19 -07:00
chore: update github PR and ISSUE templates
This commit is contained in:
+11
-10
@@ -1,7 +1,7 @@
|
||||
# Submitting an issue
|
||||
|
||||
Thank you for taking the time to report an issue or suggest a feature for PicoForge!
|
||||
<!--Submitting an issue-->
|
||||
<!--Thank you for taking the time to report an issue or suggest a feature for PicoForge! -->
|
||||
|
||||
> [!NOTE]
|
||||
Please read our [Contributing Guidelines](CONTRIBUTING.md) to understand how to get involved. If you want to work on an existing issue or a new feature, it is highly recommended to discuss it beforehand to ensure there is no conflicting code or duplicate effort.
|
||||
|
||||
<!--
|
||||
@@ -55,12 +55,13 @@ Matrix is our most preferred option for direct communication, followed by Discor
|
||||
|
||||
## Logs
|
||||
|
||||
<!-- Please provide any relevant application logs. To get console logs, you must run the application directly from your terminal. -->
|
||||
<!--
|
||||
Please provide any relevant application logs.
|
||||
To get logs, go to the application's logs view and click on copy logs button at the very bottom, then paste the logs as a text file here.
|
||||
|
||||
### Console Logs
|
||||
```text
|
||||
Paste terminal output here
|
||||
```
|
||||
On Linux, copy logs will not work, instead run the application from the termial and paste the logs here as text file.
|
||||
-->
|
||||
|
||||
### In-App Logs
|
||||
<!-- Upload screenshots of the in-app logs view here. -->
|
||||
## Screenshots/Videos
|
||||
|
||||
<!-- If problem is related to the application's UI then please provide screenshots or videos of the bug. -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Pull Request Process
|
||||
<!--# Pull Request Process-->
|
||||
|
||||
<!--
|
||||
## Before submitting a pull request
|
||||
@@ -37,7 +37,7 @@ Please check the relevant types of changes this PR introduces:
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation update
|
||||
- [ ] Refactoring / Code style change
|
||||
- [ ] Add packaging for a new platform in the release workflows
|
||||
- [ ] Add packaging for a new platform
|
||||
|
||||
### UI Changes (Optional)
|
||||
|
||||
|
||||
@@ -83,13 +83,9 @@ jobs:
|
||||
id: get_version
|
||||
shell: bash
|
||||
run: |
|
||||
# Define the path to your Cargo.toml file
|
||||
cargo_file="Cargo.toml"
|
||||
# Extract ONLY the version number using a more precise regex
|
||||
version=$(grep -m 1 '^version' "$cargo_file" | sed -E 's/.*"([0-9]+\.[0-9]+\.[0-9]+)".*/\1/')
|
||||
# Output for debugging
|
||||
echo "Version found: $version"
|
||||
# Set the output correctly for GitHub Actions
|
||||
echo "version=$version" >> $GITHUB_ENV
|
||||
|
||||
- name: install cargo-packager
|
||||
|
||||
Reference in New Issue
Block a user