Remove myself from the core team #16967
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
djuber
approved these changes
Mar 22, 2022
pr-triage
bot
added
PR: partially-approved
|
insert requisite sobbing emoji here 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 馃槶 |
juliannatetreault
approved these changes
Mar 22, 2022
pr-triage
bot
added
PR: reviewed-approved
nickytonline
deleted the
nickytonline/remove-myself-from-core-contributors
branch
pr-triage
bot
added
PR: merged
|
馃憥馃徎 LBTM (Just kidding: all the best @nickytonline!) |
|
馃槶 |
andygeorge
reviewed
Jun 6, 2022
pr-triage
bot
added
PR: reviewed-approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
Gonna miss you, friends! 馃憢馃徎
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
N/A documentation change
UI accessibility concerns?
N/A documentation change
Added/updated tests?
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.
Storybook (for Crayons components)
updated. I have filled out the
Changes Requested
issue template so Community Success can help update the Admin Docs
appropriately.
CHANGELOG.mdor in a forem.dev post
replace this line with details on why this change doesn't need to be
shared
[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?