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

docs: comment --target follow-up #430

Merged
merged 5 commits into from
Jan 13, 2023
Merged

docs: comment --target follow-up #430

merged 5 commits into from
Jan 13, 2023

Conversation

casperdcl
Copy link
Contributor

@casperdcl casperdcl commented Jan 4, 2023

  • purge actions/checkout.with.ref: ${{ github.event.pull_request.head.sha }}
  • some rewording
  • remove verbosity
  • remove unneeded --target=pr flag

Follow-up to #415

@casperdcl casperdcl added documentation Markdown files C: ref Content of /doc/*-reference C: start Content of /doc/start C: guide Content of /doc/user-guide labels Jan 4, 2023
@casperdcl casperdcl requested a review from a team January 4, 2023 12:51
@casperdcl casperdcl requested a review from a team as a code owner January 4, 2023 12:51
@casperdcl casperdcl self-assigned this Jan 4, 2023
@shcheklein shcheklein temporarily deployed to cml-dev-comment-target-stg9lfh January 4, 2023 12:51 Inactive
@casperdcl casperdcl changed the title github: purge github.event.pull_request.head.sha docs: comment --target follow-up Jan 4, 2023
@shcheklein shcheklein temporarily deployed to cml-dev-comment-target-stg9lfh January 4, 2023 12:58 Inactive
Comment on lines 32 to 35
- `--target=<pr|commit|issue</ref>>`: Where to post/associate with the comment
(`pr`, `commit`, `issue`), optionally with a reference (`issue/12`, `pr/17`,
`commit/`[rev](https://git-scm.com/docs/gitrevisions) [default: `pr` falling
back to `commit/HEAD`].
Copy link
Contributor Author

Choose a reason for hiding this comment

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

might be worth updating CLI --help to match this.

content/docs/ref/comment.md Show resolved Hide resolved
@@ -6,7 +6,7 @@ cml pr create [options] <pathspec>...

Commit specified files to a new branch and create a pull request. If sending a
report afterwards, consider using
[`cml comment update --target=pr`](/doc/ref/comment#update).
[`cml comment update`](/doc/ref/comment#update).
Copy link
Contributor Author

Choose a reason for hiding this comment

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

just double-checking: the --target=pr flag is auto-inferred here, right?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, by default the target is automatically decided based on dark magic of all sorts; see iterative/cml#1228.

Copy link
Member

Choose a reason for hiding this comment

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

Although it's not clear to me whether the documentation is suggesting users to comment on the ancillary pull request or the main one. 🤔

@github-actions
Copy link

github-actions bot commented Jan 4, 2023

Link Check Report

There were no links to check!

Co-authored-by: Helio Machado <[email protected]>
@shcheklein shcheklein temporarily deployed to cml-dev-comment-target-stg9lfh January 4, 2023 18:14 Inactive
@casperdcl casperdcl requested a review from 0x2b3bfa0 January 12, 2023 17:16
@casperdcl casperdcl merged commit 42d8e9a into master Jan 13, 2023
@casperdcl casperdcl deleted the comment-target branch January 13, 2023 07:15
@github-actions
Copy link

Link Check Report

There were no links to check!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: guide Content of /doc/user-guide C: ref Content of /doc/*-reference C: start Content of /doc/start documentation Markdown files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants