This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Chore: Open draft PR for Event Badge — @thecraftman #6
Labels
good first issue
Good for newcomers
onboarding
Newcomers, interns and mentees
Outreachy
Relates to Outreach
Milestone
Comments
Below is the link for the open draft PR for event Badge. badging/diversity-and-inclusion#2 Thanks |
Below is the link to the secret gist https://gist.github.com/thecraftman/aaaa9af6ece5a212953612659e1b14df Thanks |
@thecraftman, I put this as my first todo for Wednesday… but thanks for getting in so quickly :) |
Thank you @SMotaal . I am glad i could help and contribute |
@SMotaal @germonprez @Nebrethar Good day all, just to be clear do i still need to contribute to this badging/diversity-and-inclusion#1 for the outreachy program Thanks |
Hi @thecraftman Make sure you complete the application process by following the steps here: |
@germonprez okay, I will |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
good first issue
Good for newcomers
onboarding
Newcomers, interns and mentees
Outreachy
Relates to Outreach
Go through the README to determine how to apply for an event badge at https://github.com/badging/diversity-and-inclusion/
The goal is to open a “draft” Pull Request against master following the outlined process — feel free to creatively mock it like it is for a real event.
It helps to keep track of the steps you took in a secret gist, just the over all, nothing to detailed which can be found in the draft PR.
Place a link to this secret gist in a comment below. Please feel free to also keep notes on inconsistencies or things you felt could be improved — constructive feedback is a vital component of open collaboration.
Once you are done with the PR, place a link to to it in a comment below.
Note We will not yet review or merge PRs, we will discuss the task here and close the issue afterwards.
The text was updated successfully, but these errors were encountered: