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

refactor: improve config #813

Merged
merged 10 commits into from
Apr 9, 2023
Merged

refactor: improve config #813

merged 10 commits into from
Apr 9, 2023

Conversation

simenandre
Copy link
Contributor

No description provided.

Copy link
Contributor

@RobbieMcKinstry RobbieMcKinstry left a comment

Choose a reason for hiding this comment

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

LGTM! I don't have any color commentary to add to this, I'm afraid.

@simenandre simenandre merged commit ca33bed into master Apr 9, 2023
@simenandre simenandre deleted the improve-config branch April 9, 2023 08:50
@mikocot
Copy link
Contributor

mikocot commented Apr 11, 2023

it looks like this might have broken passing optional inputs, what was the goal and scope of the refactoring?

tgummerer added a commit that referenced this pull request May 24, 2024
…events

We only allow the `comment-on-pr` option inside of pull requests.
This makes sense because we wouldn't be able to comment on anything
otherwise.  However with the `comment-on-pr-number` option gives us a
PR number to comment on, so it can make sense with any type of GitHub
actions event.  This used to work before #813, and it looks like
disallowing this was accidental rather than intentional.

Make this work again.
tgummerer added a commit that referenced this pull request May 24, 2024
…events

We only allow the `comment-on-pr` option inside of pull requests.
This makes sense because we wouldn't be able to comment on anything
otherwise.  However with the `comment-on-pr-number` option gives us a
PR number to comment on, so it can make sense with any type of GitHub
actions event.  This used to work before #813, and it looks like
disallowing this was accidental rather than intentional.

Make this work again.
tgummerer added a commit that referenced this pull request May 28, 2024
…events

We only allow the `comment-on-pr` option inside of pull requests.
This makes sense because we wouldn't be able to comment on anything
otherwise.  However with the `comment-on-pr-number` option gives us a
PR number to comment on, so it can make sense with any type of GitHub
actions event.  This used to work before #813, and it looks like
disallowing this was accidental rather than intentional.

Make this work again.
tgummerer added a commit that referenced this pull request May 28, 2024
…events (#1178)

We only allow the `comment-on-pr` option inside of pull requests.
This makes sense because we wouldn't be able to comment on anything
otherwise.  However with the `comment-on-pr-number` option gives us a
PR number to comment on, so it can make sense with any type of GitHub
actions event.  This used to work before #813, and it looks like
disallowing this was accidental rather than intentional.

Make this work again.
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.

3 participants