updates header in readme #5
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
bc-micah
reviewed
May 6, 2024
bc-micah
reviewed
May 6, 2024
bc-micah
reviewed
May 6, 2024
Co-authored-by: Micah Thomas <[email protected]>
Co-authored-by: Micah Thomas <[email protected]>
deov31
reviewed
May 7, 2024
deov31
approved these changes
May 13, 2024
bc-marco
added a commit
that referenced
this pull request
May 31, 2024
* fix: implementing fix for images in readme file (#7) * chore: updates header in readme (#5) --------- Co-authored-by: Estefania Ocampo <[email protected]> Co-authored-by: Katie Hoesley <[email protected]>
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?
Write a description of the changes you're making here, and decisions that you made
along the way. Provide enough context that the reviewer(s) can understand your
changes, and the intent behind them. For more details refer to contributing guideline
Why?
Describe the underlying driver or intent behind this change. Provide some context
on why it's needed or what is the intended use. For more details refer to contributing guideline
Testing / Proof
Explain what you did to test and ensure that these changes work the way you expect.
You must provide evidence in the form of unit tests, screenshots, logs, API
payloads or other output to show the expected behaviour. For more details refer to contributing guideline
How can this change be undone in case of failure?
Provide experiments, feature flags or other mechanisms which used to reduce the risk of changes introduced in this PR. For more details refer to contributing guideline
ping {suggested reviewers}