Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Create a pre-work onboarding issue template for general DevOps CoP members

Ouverte
  • Quelque chose ne va pas ?
#195 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
57/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
Active
Stack technique
github, markdown
Domaine
devops, documentation

Piste de recherche

Commencez par examiner .github/ISSUE_TEMPLATE/pre-work-template-devops-security.md et les templates devops existants, puis confirmez les attentes générales concernant les membres avec les leads. Créez le template Markdown en libre-service dans .github/ISSUE_TEMPLATE/, mettez à jour config.yml si nécessaire et excluez les étapes AWS/Terraform. Le travail est terminé lorsque le template mergé apparaît dans le New issue picker sur master et crée une issue correctement étiquetée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

complexity: medium feature: templates role: DevOps Engineer size: 3pt
Overview

We need an onboarding issue that a new DevOps CoP member can open for themselves, because right
now one does not exist. devops has templates only for onboarding and offboarding leads, and
those are performed by an existing lead rather than by the newcomer. devops-security has a
self-serve pre-work checklist, but it is specific to that repo and takes the member through
creating a personal AWS account and running Terraform. A person who joins the CoP and is not
going to work on devops-security therefore has no onboarding issue at all, and nothing tracks
whether they ever got set up.

Action Items
  • Confirm with the leads what a general CoP member is actually expected to do in their first
    two weeks. This is the part that needs a decision, not just drafting — the answer
    determines everything below.
  • Write the template into .github/ISSUE_TEMPLATE/ as a markdown template, following the
    shape of devops-security's pre-work template: self-assign, pick a role label, set status,
    add to the board, attend the meeting.
  • Set labels: in the frontmatter. Note devops has no equivalent of devops-security's
    complexity: prework label — decide whether to add one or use complexity: small.
  • Keep the AWS and Terraform steps out. If a member later joins devops-security work, they
    open that repo's pre-work issue then. Link to it rather than duplicating it.
  • Add the template to .github/ISSUE_TEMPLATE/config.yml if that file gates what appears in
    the picker.
  • After the PR merges, go to the repo's "New issue" page and confirm the template appears and
    produces a correctly labelled issue. GitHub renders the picker from the default branch
    only, so this cannot be verified from your branch.
Resources/Instructions
  • Shape to follow: pre-work-template-devops-security.md
  • What devops has today: onboard-ops-cop-lead.md, offboard-ops-cop-lead.md,
    recruit-new-lead.md, post-an-open-role.md, plus the two blank forms — none of them is a
    member self-onboarding issue
  • The default branch of devops is master, not main
  • This template is what the team-side checklist (sibling issue) will point new members at, so the
    two should agree on what the member is asked to do
Langage dominant
PowerShell
Étoiles
8
Forks
10
Merge moyen
5 h 34 min
PR mergées (30 j)
17

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de hackforla/devops

Toutes les issues de hackforla/devops

Issues similaires

Plus d'issues DevOps

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.