forked from hinterland/documentation
docs: remove priority lable from ISSUE.md
This commit is contained in:
@@ -78,11 +78,6 @@ Apply appropriate labels to categorize and prioritize issues.
|
||||
- `chore`
|
||||
- `revert`
|
||||
|
||||
- ### Priority:
|
||||
- `priority: low`
|
||||
- `priority: medium`
|
||||
- `priority: high`
|
||||
|
||||
- ### Status:
|
||||
- `status: needs triage`
|
||||
- `status: in progress`
|
||||
@@ -113,7 +108,6 @@ When creating an issue, use the appropriate template:
|
||||
- Environment (OS, software vesions if possible)
|
||||
- **Labels**:
|
||||
- `bug`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Feature Request
|
||||
@@ -126,7 +120,6 @@ When creating an issue, use the appropriate template:
|
||||
- Additional Context
|
||||
- **Labels**:
|
||||
- `feature`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Refactor Task
|
||||
@@ -138,7 +131,6 @@ When creating an issue, use the appropriate template:
|
||||
- Expected Benefits
|
||||
- **Labels**:
|
||||
- `refactor`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Documentation Task
|
||||
@@ -149,7 +141,6 @@ When creating an issue, use the appropriate template:
|
||||
- Proposed Changes
|
||||
- **Labels**:
|
||||
- `documentation`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Performance Improvement
|
||||
@@ -162,7 +153,6 @@ When creating an issue, use the appropriate template:
|
||||
- Additional Information
|
||||
- **Labels**:
|
||||
- `performance`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Test Task
|
||||
@@ -175,7 +165,6 @@ When creating an issue, use the appropriate template:
|
||||
- Additional Context
|
||||
- **Labels**:
|
||||
- `test`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Build Task
|
||||
@@ -188,7 +177,6 @@ When creating an issue, use the appropriate template:
|
||||
- Impact
|
||||
- **Labels**:
|
||||
- `build`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### CI Task
|
||||
@@ -201,7 +189,6 @@ When creating an issue, use the appropriate template:
|
||||
- Impact
|
||||
- **Labels**:
|
||||
- `ci`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Chore Task
|
||||
@@ -213,7 +200,6 @@ When creating an issue, use the appropriate template:
|
||||
- Impact
|
||||
- **Labels**:
|
||||
- `chore`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
### Revert Task
|
||||
@@ -225,7 +211,6 @@ When creating an issue, use the appropriate template:
|
||||
- Impact
|
||||
- **Labels**:
|
||||
- `chore`
|
||||
- `priority: {high|medium|low}`
|
||||
- `status: needs triage`
|
||||
|
||||
## Referencing Issues and Pull Requests
|
||||
@@ -244,7 +229,7 @@ When creating an issue, use the appropriate template:
|
||||
## Workflow
|
||||
1. **Search Before Posting**: Check if a similar issue already exists.
|
||||
2. **Create the Issue**: Use the correct template and follow the conventions.
|
||||
3. **Label Appropriately**: Add relevant lables for type, priority and status.
|
||||
3. **Label Appropriately**: Add relevant lables for type and status.
|
||||
4. **Assign and Milestones**: Assign yourself if working on it and add to a milestone if applicable.
|
||||
5. **Discussion**: Use the issue comments for any discussion or clarification.
|
||||
6. **Link Pull Requests**: When submitting a PR, reference the issue it addresses.
|
||||
@@ -258,22 +243,21 @@ Feature: Implement note graph visualization
|
||||
|
||||
Labels:
|
||||
- feature
|
||||
- priority: medium
|
||||
- status: needs triage
|
||||
|
||||
Description:
|
||||
|
||||
**Overview:**
|
||||
# Overview
|
||||
Implement a visual graph representation of notes showing their connections.
|
||||
|
||||
**Motivation:**
|
||||
# Motivation
|
||||
Helps users understand relationships between notes at a glance.
|
||||
|
||||
**Proposed Solution:**
|
||||
# Proposed Solution
|
||||
- Use D3.js for rendering the graph.
|
||||
- Nodes represent notes; edges represent links.
|
||||
|
||||
**Additional Context:**
|
||||
# Additional Context
|
||||
- Related to the discussion in #400.
|
||||
```
|
||||
|
||||
@@ -284,30 +268,29 @@ Bug: Unable to save notes with special characters
|
||||
|
||||
Labels:
|
||||
- bug
|
||||
- priority: high
|
||||
- status: needs triage
|
||||
|
||||
Description:
|
||||
|
||||
**Overview:**
|
||||
# Overview
|
||||
Notes containing special characters like `&`, `<`, and `>` are not saved correctly.
|
||||
|
||||
**Steps to Reproduce:**
|
||||
# Steps to Reproduce
|
||||
1. Create a new note.
|
||||
2. Include special characters in the content.
|
||||
3. Save the note.
|
||||
4. Reopen the note.
|
||||
|
||||
**Expected Behavior:**
|
||||
# Expected Behavior
|
||||
The note content is saved and displayed correctly.
|
||||
|
||||
**Actual Behavior:**
|
||||
# Actual Behavior
|
||||
Special characters are either stripped out or cause display issues.
|
||||
|
||||
**Environment:**
|
||||
# Environment
|
||||
- Application Version: 1.2.3
|
||||
- OS: Windows 10
|
||||
|
||||
**Additional Information:**
|
||||
# Additional Information
|
||||
- Possibly related to encoding issues.
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user