Originally created by @odenix on GitHub (Feb 14, 2024).
When an external contributor submits a PR, CI builds are on hold until manually authorized by a team member. This complicates external contributions as we won't know the build outcome for a long time. Is there a way to alleviate this pain?
PS: Out of curiosity, why did you choose CircleCI over GitHub Actions?
Originally created by @odenix on GitHub (Feb 14, 2024).
When an external contributor submits a PR, CI builds are on hold until manually authorized by a team member. This complicates external contributions as we won't know the build outcome for a long time. Is there a way to alleviate this pain?
PS: Out of curiosity, why did you choose CircleCI over GitHub Actions?
We're working on a process to run CI for high volume contributors.
For CircleCI vs. GitHub Actions: I don't have an answer for you here, unfortunately!
@bioball commented on GitHub (Feb 23, 2024):
We're working on a process to run CI for high volume contributors.
For CircleCI vs. GitHub Actions: I don't have an answer for you here, unfortunately!
For CircleCI vs. GitHub Actions: I don't have an answer for you here, unfortunately!
Would you accept a PR that moves from CircleCI to GitHub Actions? 🤔
@StefMa commented on GitHub (Nov 21, 2024):
> For CircleCI vs. GitHub Actions: I don't have an answer for you here, unfortunately!
Would you accept a PR that moves from CircleCI to GitHub Actions? 🤔
Would you accept a PR that moves from CircleCI to GitHub Actions?
This would be a significant step forward for contributors, enabling them to
run GitHub Actions on their Pkl forks
contribute CI improvements such as #225 (which for some reason isn't moving forward)
I've noticed that some Apple OSS projects already use GitHub Actions.
@odenix commented on GitHub (Nov 23, 2024):
> Would you accept a PR that moves from CircleCI to GitHub Actions?
This would be a significant step forward for contributors, enabling them to
* run GitHub Actions on their Pkl forks
* contribute CI improvements such as #225 (which for some reason isn't moving forward)
I've noticed that some Apple OSS projects already use GitHub Actions.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @odenix on GitHub (Feb 14, 2024).
When an external contributor submits a PR, CI builds are on hold until manually authorized by a team member. This complicates external contributions as we won't know the build outcome for a long time. Is there a way to alleviate this pain?
PS: Out of curiosity, why did you choose CircleCI over GitHub Actions?
@bioball commented on GitHub (Feb 23, 2024):
We're working on a process to run CI for high volume contributors.
For CircleCI vs. GitHub Actions: I don't have an answer for you here, unfortunately!
@odenix commented on GitHub (Oct 19, 2024):
Any progress? This is the biggest pain point of contributing to Pkl.
@StefMa commented on GitHub (Nov 21, 2024):
Would you accept a PR that moves from CircleCI to GitHub Actions? 🤔
@odenix commented on GitHub (Nov 23, 2024):
This would be a significant step forward for contributors, enabling them to
I've noticed that some Apple OSS projects already use GitHub Actions.