🏷️ Discussion TypeBug 💬 Feature/Topic AreaARC (Actions Runner Controller) Discussion DetailsIsn't the FUNDING.yml for Sponsors? It shouldn't trigger an action at all. |
Replies: 3 comments 2 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
You're right that GitHub Actions treats every The fix is to move the file up one level:
If the file is not in |
|
You're right! The issue is likely its location. GitHub expects the file at Move it one directory up, and GitHub Actions should stop attempting to process it as a workflow while the Sponsor button continues to work. |
You're right that
FUNDING.ymlis only for the Sponsor button. The path in the error is the clue:.github/workflows/FUNDING.yml.GitHub Actions treats every
.yml/.yamlfile inside.github/workflows/as a workflow definition, regardless of its name. A funding file has noon:orjobs:keys, so Actions tries to load it on each push, finds nothing to run, and reports a failed run with "No jobs were run".The fix is to move the file up one level:
.github/FUNDING.ymlon the default branch is the location the Sponsor button reads from, so the button keeps working and the failed run…