Files
3DPrintMeetup/.github/copilot-instructions.md
2025-12-02 14:10:47 -06:00

57 lines
1.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
````instructions
# GitHub Copilot Instructions
**Never use the unicode multiplication symbol (×, U+00D7) in any documentation, code, or markdown.**
Always use a plain lowercase 'x' for dimensions and multiplication.
- WRONG: `25mm × 25mm × 25mm`
- CORRECT: `25mm x 25mm x 25mm`
# Git Instructions
- If a git command fails due to authentication reasons, retry the command exactly once.
# Wiki Tagging Standards
All wiki pages should use YAML frontmatter for tagging.
## Challenge Tags
All challenge pages must include the following tags:
- `challenge`: Identifies the page as a challenge.
- `challenge-NNN`: A unique sequential identifier.
- `challenge-001`: October 2025
- `challenge-002`: November 2025
- `challenge-003`: December 2025
- Increment for subsequent months.
- `archive`: (Optional) Use this tag when the challenge is no longer active.
## Visibility Tags
- `hidden`: Use this tag to prevent the page from being published to the fargo3d.com website.
# Content Synchronization
The `wiki-fargo3d` submodule contains the official documentation. Some content is mirrored in the main repository root.
- **Readme.md vs wiki-fargo3d/Home.md**: Keep announcements and general descriptions in sync.
- **challenges.md vs wiki-fargo3d/Current-Challenge.md**: `challenges.md` should reflect the active challenge found in the wiki.
- **itinerary.md vs wiki-fargo3d/Itinerary.md**: Keep meeting schedules in sync.
## Git Workflow for Wiki Updates
1. Make changes in `wiki-fargo3d/`.
2. Commit and push changes in `wiki-fargo3d`.
3. Go to root `P:\3dPrintMeetup`.
4. Commit the submodule update.
5. Push root changes.
## Example Front Matter
```yaml
---
tags:
- challenge
- challenge-002
---
```
````