fix: make text in inline code blocks visible #38

Merged

naomi merged 1 commits from fix/inline-code-block-colors into main 2026-07-02 00:39:22 -07:00

Conversation 0 Commits 1 Files Changed 1

+14

ilenia commented 2026-06-30 14:46:35 -07:00

Member

Copy Link

Copy Source

Explanation

dark mode before

dark mode after

light mode before

light mode after

I copied from the code blocks that are used in the style guide to be sure to use approved colors

Issue

No response

Attestations

• I have read and agree to the Code of Conduct
• I have read and agree to the Community Guidelines.
• My contribution complies with the Contributor Covenant.

Dependencies

• I have pinned the dependencies to a specific patch version.

Style

• I have run the linter and resolved any errors.
• My pull request uses an appropriate title, matching the conventional commit standards.
• My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.

Tests

• My contribution adds new code, and I have added tests to cover it.
• My contribution modifies existing code, and I have updated the tests to reflect these changes.
• All new and existing tests pass locally with my changes.
• Code coverage remains at or above the configured threshold.

Documentation

No response

Versioning

Patch - My pull request introduces bug fixes ONLY.

### Explanation dark mode before  dark mode after  light mode before  light mode after  I copied from the code blocks that are used in the style guide to be sure to use approved colors ### Issue _No response_ ### Attestations - [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [ ] I have pinned the dependencies to a specific patch version. ### Style - [x] I have run the linter and resolved any errors. - [x] My pull request uses an appropriate title, matching the conventional commit standards. - [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [ ] My contribution adds new code, and I have added tests to cover it. - [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [ ] All new and existing tests pass locally with my changes. - [ ] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning Patch - My pull request introduces bug fixes ONLY.

image.png

56 KiB

image.png

68 KiB

image.png

58 KiB

image.png

76 KiB

ilenia force-pushed fix/inline-code-block-colors from bffe5ce8b4 to 5a1c9b474b 2026-07-02 00:20:39 -07:00 Compare

ilenia added 1 commit 2026-07-02 00:22:48 -07:00

fix: make text in inline code blocks visible 194e5a0475

ilenia force-pushed fix/inline-code-block-colors from 5a1c9b474b to 194e5a0475 2026-07-02 00:22:48 -07:00 Compare

naomi merged commit 52afd3c1ce into main 2026-07-02 00:39:22 -07:00

naomi deleted branch fix/inline-code-block-colors 2026-07-02 00:39:22 -07:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

aspect

code

Concerns the software code in the repository

aspect

dx

Concerns developers' experience with the codebase

aspect

interface

Concerns end-users' experience with the software

aspect

text

Concerns the documentation material in the repository

contribute

good first issue

A great opportunity for a team member to learn a new codebase

contribute

help wanted

Open for anyone on our team to grab.

contribute

staff only

Restricted to our executive leadership.

goal

addition

Addition of new feature

goal

fix

Bug fix

goal

improvement

Improvement to an existing feature

points

1

Very simple issue requiring minimal effort and complexity.

points

13

Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.

points

2

Simple issue that requires a bit more thought or investigation.

points

3

Moderate complexity issue requiring more substantial work.

points

5

Complex issue requiring significant effort and expertise.

points

8

Very complex issue requiring extensive work and deep expertise.

priority

critical

1

Must be fixed ASAP

priority

high

2

Stalls work on the project or its dependents

priority

low

4

Low priority and doesn't need to be rushed

priority

medium

3

Not blocking but should be fixed soon

priority

none

5

No priority, should only be performed when a developer is available

status

awaiting triage

Has not been triaged & therefore, not ready for work

status

blocked

Blocked and therefore not ready for work

status

discarded

Will not be worked on

status

discontinued

Not suitable for work as repo is in maintenance

status

label work required

Needs proper labelling before it can be worked on

status

ready for dev

Ready for work

status

ticket work required

Needs more details before it can be worked on

talk

discussion

Open for discussions and feedback

talk

question

Can be resolved with an answer

time

1 day

Approximately one full day of development work.

time

1-2 weeks

One to two weeks of focused development effort.

time

2-3 days

Two to three days of development effort.

time

4-5 days

Approximately one week of development work.

time

<1 day

Less than one day of focused work. Quick fixes or simple tasks.

time

>2 weeks

More than two weeks of development work. Must be broken down into smaller pieces.

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

gurkirat hanna (Hanna Rose) hikari (Hikari) ilenia minori (Minori) naomi (Naomi Carrigan) rain teklu tim

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: nhcarrigan/docs#38