Skip to content

doc: clarify the behavior of a pull_request event #1627

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

Closed
wants to merge 1 commit into from
Closed

doc: clarify the behavior of a pull_request event #1627

wants to merge 1 commit into from

Conversation

cjc7373
Copy link

@cjc7373 cjc7373 commented Feb 27, 2024

fixes #426

May be the words can be improved. But I think it's necessary to drop a kind notice in the README.

@cjc7373 cjc7373 requested a review from a team as a code owner February 27, 2024 10:53
@cory-miller
Copy link
Contributor

I'm going to close this in favor or referring to the documentation page:

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request

@ahans
Copy link

ahans commented May 12, 2025

I tend to read the docs first before looking through issues to find the answer to some questions. Having this extra sentence in the docs wouldn't hurt at all (and you could in fact even include the link to that GH page there).

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.

What does "Checkout pull request HEAD commit instead of merge commit" mean?
3 participants