Skip to content

Latest commit

 

History

History
58 lines (38 loc) · 2.8 KB

File metadata and controls

58 lines (38 loc) · 2.8 KB

Contributing

Thanks for your interest in contributing to the Advanced Copilot CLI course! This repository hosts the course content — the Markdown modules in content/ that make up the hands-on lessons.

Code of Conduct

This project is released with a Contributor Code of Conduct. By participating, you agree to abide by its terms.

Contributions are released under the project's open source license.

What to read first

If you want to author or edit content, start with the Markdown conventions — the house style every .md file in this repo follows (reference-style links, no hard-wrapped paragraphs, GitHub admonition syntax, sentence-case headings, and the module cross-linking pattern). For how the course maps onto the downstream Learning Hub, see PUBLISHING.md.

Module files live in content/, numbered NN-short-slug.md. The H1 is the module title, and adjacent modules cross-link through reference definitions at the bottom of each file — follow an existing module for the pattern.

Submitting a pull request

  1. Fork and clone the repository.
  2. Create a topic branch (git checkout -b my-change).
  3. Make your change. Keep PRs focused — one logical change per PR.
  4. Push to your fork and open a pull request.
  5. Wait for review.

Before you push

  • Confirm your Markdown follows the conventions — run through the validation checklist at the bottom of that file.
  • Check that every internal link resolves and that any content you built or previewed renders as expected.

Commit messages

Conventional commit prefixes preferred: docs:, chore:, fix:, ci:, feat:.

Include a Co-authored-by trailer when AI-assisted:

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

A note on catch-up branches

The learner-facing catch-up branches (start-of-module-N) live in the companion contoso-inventory repository and are machine-generated from this course content. Author your changes to the modules here — never edit those branches directly.

Resources