-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add pull_request to on events list for CI #4604
Conversation
This is needed for pull requests submitted via forks.
No I won't. I can do it now they've passed 😄 |
And yes, it is known that certain events that happen when modifying a pull request, eg labelling, requesting reviewers etc, cause CI to run again even if the actual code hasn't changed. The ability to filter those is coming 🔜 |
Would it be possible to use GitHub Actions to automate some of our scripts? Stuff like I know absolutely nothing about GitHub Actions, so forgive me if this is a dumb question. |
Most definitely, though I'm not sure how much success we'd have with automating |
Oooof. Looks like something has changed around the UTF-8 encoding on the underlying CI env since the tests on this PR last passed and merging. Digging into it now. |
Try setting |
Read my mind. It was the the first thing I was going to try as Docker has the same issue and really should have remembered this as I stumble upon it almost every time I touch docker 😄 |
Heh. Since a Docker port doesn't exist on OpenBSD, I actually solved two problems at once by having a shell-script named #!/bin/sh
export LANG=en_AU.UTF-8 Not sure if this is the best or worst hack I've ever thought of (okay, definitely not the worst...). I can't export |
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml -on: [push] jobs:
|
Description
When switching from Travis to GitHub Actions, I missed out that we need to trigger builds for the
pull_request
event else CI won't run for PRs submitted from forks.This isn't very clear from the docs or the available examples.
I'm also taking this opportunity to use more descriptive names so the checks look better.
Before:
After:
I'll update the list of required status checks once this PR has been merged.
[Template removed as it is not relevant]