devcontainers / devcontainers/.github
> ### Code of Conduct
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 10
- Forks
- 2
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
> ### Code of Conduct
>
> - [x] I have read and agree to the GitHub Docs project's [Code of Conduct](https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md)
>
> ### Pre-requisites
>
> - [x] My application to the GitHub Technology Partner Program is approved.
>
> ### Tasks
>
> - [x] MUST follow our [general contributing guidelines](https://docs.github.com/en/contributing) for voice and markup format.
> - [x] MUST emphasize how the third-party product works with GitHub.
> - [x] MUST be written in Markdown format, using [one of the templates provided](https://docs.github.com/en/contributing/writing-for-github-docs/templates).
> - [x] MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the `contributor.name` and `contributor.URL` properties in the template's YAML frontmatter.
> - [x] MUST be proposed via a pull request to this repo following [the GitHub Flow](https://guides.github.com/introduction/flow/).
> - [x] MUST be located in the root of [the `content` folder](content). Your filename MUST match the GitHub technology partner name, and use the `.md` file extension.
>
> ### Pull Request
>
> - [x] MUST reference this issue, e.g. via `closes [this issue number]`.
> - [x] MUST pass the automated CI checks.
> - [x] MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, _or_ a video / screencast walkthrough).
_Originally posted by @nvt261991-sys in https://github.com/github/docs/issues/43056#issuecomment-3936862540_
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Consultez les directives de contribution, les modèles disponibles et le dossier de contenu racine avant de commencer. L’issue n’identifie ni le partenaire technologique ni le sujet de la documentation ; établissez donc d’abord ces détails. La finalisation nécessite un fichier Markdown nommé d’après le partenaire, avec les métadonnées de contributor requises, les liens de référence et un CI réussi.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- content, documentation
- Type d'issue
- Documentation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 20/100