Add content synchronization instructions
This commit is contained in:
17
.github/copilot-instructions.md
vendored
17
.github/copilot-instructions.md
vendored
@@ -1,3 +1,4 @@
|
||||
````instructions
|
||||
# GitHub Copilot Instructions
|
||||
|
||||
**Never use the unicode multiplication symbol (×, U+00D7) in any documentation, code, or markdown.**
|
||||
@@ -28,6 +29,21 @@ All challenge pages must include the following tags:
|
||||
## 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
|
||||
@@ -37,3 +53,4 @@ tags:
|
||||
- challenge-002
|
||||
---
|
||||
```
|
||||
````
|
||||
|
||||
Reference in New Issue
Block a user