Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor fixes for GitHub docs #403

Merged
merged 3 commits into from
May 17, 2023
Merged

Minor fixes for GitHub docs #403

merged 3 commits into from
May 17, 2023

Conversation

castrapel
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented May 11, 2023

Codecov Report

Patch coverage has no change and project coverage change: +0.04 🎉

Comparison is base (f05b180) 85.23% compared to head (7cd78cc) 85.28%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #403      +/-   ##
==========================================
+ Coverage   85.23%   85.28%   +0.04%     
==========================================
  Files          98       98              
  Lines       10677    10677              
==========================================
+ Hits         9101     9106       +5     
+ Misses       1576     1571       -5     
Flag Coverage Δ
functional_tests 66.89% <ø> (ø)
functional_tests_config_discovery 47.13% <ø> (+0.04%) ⬆️
unit_tests 75.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

8. Once your reviewer approves your changes, add comment `iambic apply` to have iambic apply the changes. If the changes can be successfully applied, the PR will be automatically merged into main as well.
5. Create a pull request.
6. The installed GitHub App will comment with plan the changes. Any time you want iambic github action to re-plan the changes, you can comment `iambic plan`.
7. The plan will be a comment in line, as long as it is less than 65kb. (Be very careful with big plans because those are difficult for reviewers to review.) <!-- #TODO So then what? What's the alternative? -->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not holding anything up but I thought if the output of plan exceeded the make size for a comment we wrote it to a gist? Not sure if that's actually implemented or has even been formally defined though.

Will-NOQ
Will-NOQ previously approved these changes May 12, 2023
Copy link
Collaborator

@Will-NOQ Will-NOQ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@castrapel castrapel merged commit c596fd3 into main May 17, 2023
4 checks passed
@castrapel castrapel deleted the chore/minor_gh_doc_fixes branch May 17, 2023 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants