Change handbook link on members homepage to key code orientation link. #763
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
|
Same as #762 -- it looks like the brakeman check is failing because the current Ruby version (2.7.6) is nearing end of life. I'm not sure if the failing check blocks merging this PR or not. |
Discussed during the membership committee meeting on 2/1/23. The handbook is very long, and probably what most people need to know is how to get into the DU space. The key code orientation slide deck explains how to get into the DU space more concisely.
sarahwalters
force-pushed
the
sw/space-entry-link
branch
from
8668005
to
21f76d4
Compare
|
The failing check was fixed on main -- rebased past that change and these checks are passing now. |
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 github issue is this PR for, if any?
Didn't file an issue.
What does this code do, and why?
Change the handbook link on members homepage to the key code orientation link.
Discussed during the membership committee meeting on 2/1/23. The handbook is very long, and probably what most people need to know is how to get into the DU space. The key code orientation slide deck explains how to get into the DU space more concisely.
How is this code tested?
Locally -- screenshot below.
No unit tests needed because this is just a text change.
Are any database migrations required by this change?
No
Are there any configuration or environment changes needed?
No
Screenshots please :)
I tried the new "Key code orientation" link to make sure it goes to the right place.