Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enhance Template:
issue feedback
This addition explicitly requests users to provide relevant data or data extracts along with their feedback. It emphasizes the importance of data in supporting discussions and decision-making while reminding submitters to ensure that the data is anonymized and compliant with privacy guidelines.
Enhance Template:
discussion Topic
This YAML replaces the previous
discussion-topic.md
file. It defines the structure and content of the GitHub issue form for discussing broad topics within the FOCUS community. It ensures that all necessary information is gathered effectively, including an optional field for attaching relevant data, which will support the discussion with tangible examples.Enhance Template:
maintenance
This YAML template is structured to gather essential information about maintenance tasks within the GitHub repository or actions. The format ensures clarity and specificity in the task descriptions and outcomes, facilitating effective task management and completion.
Enhance Template:
spec-change
This template provides a YAML format for submitting specification changes, ensuring that all relevant information is captured, including the type of issue, whether the issue is normalized, a detailed description, a clear definition of what constitutes completion of the task, and an optional section for additional context or supporting information. This approach ensures clarity and facilitates the efficient management of specification changes.