Skip to content

Conversation

@FeynmanZhou
Copy link
Member

@FeynmanZhou FeynmanZhou commented Nov 20, 2023

Resolve #824

This guideline only includes the guiding principles for Notation CLI error message. All suggested changes will be documented into different GitHub issues and another document.

@codecov-commenter
Copy link

codecov-commenter commented Nov 20, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.27%. Comparing base (31c9e84) to head (a0fe8af).
Report is 81 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #834      +/-   ##
==========================================
+ Coverage   64.09%   71.27%   +7.17%     
==========================================
  Files          40       45       +5     
  Lines        2284     2169     -115     
==========================================
+ Hits         1464     1546      +82     
+ Misses        698      429     -269     
- Partials      122      194      +72     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@FeynmanZhou FeynmanZhou marked this pull request as ready for review December 13, 2023 07:49
Copy link
Contributor

@yizha1 yizha1 left a comment

Choose a reason for hiding this comment

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

Thanks, @FeynmanZhou While we may not provide an exhaustive list of examples in this guide, I would suggest this PR provides a general guideline. We can create another issue to track improvements for each command.

ghost
ghost previously approved these changes Jan 9, 2024
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

LGTM

@FeynmanZhou
Copy link
Member Author

I will move all suggested changes for those examples into different GitHub issues. All comments above are related to examples so I will address them in separate issues. But I will mark those comments as resolved first.

@FeynmanZhou FeynmanZhou requested a review from JeyJeyGao January 11, 2024 01:19
@FeynmanZhou FeynmanZhou requested a review from yizha1 January 24, 2024 01:38
@github-actions
Copy link

This PR is stale because it has been opened for 45 days with no activity. Remove stale label or comment. Otherwise, it will be closed in 30 days.

@github-actions github-actions bot added the Stale label Mar 22, 2024
@yizha1 yizha1 removed the Stale label Mar 22, 2024
@yizha1 yizha1 added this to the 1.2.0 milestone Mar 22, 2024
@FeynmanZhou FeynmanZhou requested a review from shizhMSFT April 8, 2024 16:03
@FeynmanZhou FeynmanZhou requested review from a user and priteshbandi April 8, 2024 16:03
@FeynmanZhou
Copy link
Member Author

I am curious why this doc PR broken the Codecov? It doesn't have any code change.

@FeynmanZhou FeynmanZhou force-pushed the error-msg branch 2 times, most recently from 1cf0556 to ca096da Compare May 27, 2024 10:23
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Copy link
Contributor

@JeyJeyGao JeyJeyGao left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

LGTM

priteshbandi pushed a commit that referenced this pull request May 28, 2024
This error message improvement is based on the Notation CLI error message improvement guideline that we defined in #834

Resolve part of #934 
Signed-off-by: Junjie Gao <junjiegao@microsoft.com>
Copy link
Contributor

@priteshbandi priteshbandi left a comment

Choose a reason for hiding this comment

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

LGTM

@priteshbandi priteshbandi merged commit 66126e2 into notaryproject:main May 28, 2024
7h3-3mp7y-m4n pushed a commit to 7h3-3mp7y-m4n/notation that referenced this pull request Mar 29, 2025
This error message improvement is based on the Notation CLI error message improvement guideline that we defined in notaryproject#834

Resolve part of notaryproject#934 
Signed-off-by: Junjie Gao <junjiegao@microsoft.com>
7h3-3mp7y-m4n pushed a commit to 7h3-3mp7y-m4n/notation that referenced this pull request Mar 29, 2025
…ject#834)

Resolve notaryproject#824 

This guideline only includes the guiding principles for Notation CLI error message. All suggested changes will be documented into different GitHub issues and another [document](https://hackmd.io/9O01p9xYS7S-8apWZkaLHg).

---------
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
FeynmanZhou pushed a commit to FeynmanZhou/notation that referenced this pull request May 15, 2025
This error message improvement is based on the Notation CLI error message improvement guideline that we defined in notaryproject#834

Resolve part of notaryproject#934 
Signed-off-by: Junjie Gao <junjiegao@microsoft.com>
FeynmanZhou added a commit to FeynmanZhou/notation that referenced this pull request May 15, 2025
…ject#834)

Resolve notaryproject#824 

This guideline only includes the guiding principles for Notation CLI error message. All suggested changes will be documented into different GitHub issues and another [document](https://hackmd.io/9O01p9xYS7S-8apWZkaLHg).

---------
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
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.

Create a CLI Error Handling Guideline to improve error messages and error handling

6 participants