I'm trying to use Lighhouse CI Action for my Github Actions workflows.
It works well with public pages.
I'm not used to using these tools, merely helping a team get it into their workflow.
My question is, is there a way to run these audits on deployed environments that sit behind authentication?
Or do I need to use the staticDistDir way?
This is primarily in the PR workflows. For when we merge to main and go public, we audit the new page.
- name: Audit URLs using Lighthouse
uses: treosh/lighthouse-ci-action#v7
id: lighthouse_audit
with:
urls: |
https://www.example.com/
budgetPath: ./.github/workflows/budget.json
uploadArtifacts: true
temporaryPublicStorage: true
What I would love to do is have flags for basic auth as well.
Related
I am giving a coding lesson where students can upload answers to our quizzes using personal, private repositories. So here's how the repository structure of my organization looks like:
my_organization/student_1_project
my_organization/student_2_project
my_organization/...
my_organization/student_n_project
I would like to run a private GitHub Action at any push on a student repository. This Action would run partial reviews of the student's work, and notify me of stuffs. Its code would need to be unreachable from students, of course, otherwise providing hints & solutions.
I have three questions:
Can my workflow in e.g. my_organization/student_2_project be to use a private action my_organization/my_private_action? It seems like yes thanks to actions/checkout#v2 (see here) but pretty sure that involves playing with keys or tokens or secrets - I'm not so at ease with that and currently get an error although it does exist:
Error: fatal: repository 'https://github.com/my_organization/my_private_action' not found
Can it prevent the student (owner/admin of my_organization/student_2_project) to see the code in my_organization/my_private_action?
With the same constraints, could the private action be hosted in another organization?
Thanks a lot for your help!
This is how I understand the restrictions:
Using an action from a private/internal repository currently isn't supported directly, see this issue on the roadmap. A possible workaround is adding a personal access token with access to the private repo that contains the action and then checking it out like this:
- name: Get private repo with action
uses: actions/checkout#v2
with:
repository: yourorg/privateactionrepo
ref: master
token: ${{ secrets.PAT_TOKEN }}
path: .github/actions
You can then use the action in another step like
uses: ./.github/actions/actionname
The PAT can be a secret on the org level so you don't have to add it to every single student repo.
Since the student's repo has access to the PAT, they can use it to create a workflow that checks out the private repo and does whatever they want with it – upload its contents, print every file etc.
As long as the PAT has the permissions to check out the repo containing the action, the action can live anywhere, including in another organization.
Alternatively, if you want to prevent your students from seeing your action, you could add a workflow to your students' repositories that sends a request to the GitHub API and then have a trigger in your action on the repository_dispatch event.
Can you please tell me if it is possible to setup Github action which gets triggered
when a new issue opened against a repo?
If not, is there other way which I can automated when a new issue is filed in a repo?
Forllowing the GitHub workflow syntax for on.<event_name>.types, you can trigger an action on a new issue with:
name: "Set Issue Label and Assignee"
on:
issues:
types: [opened]
Example: Naturalclar/issue-action
Webhooks are not needed here:
Subcribing to a webhook event like the one for issues is not enough: you need to setup a listener which will process the JSON payload. (for instance, building a GitHub App with ProBot).
"if not": GitHub Actions are there to avoid using webhooks, if your project is on GitHub.com (webhooks can still be useful for on premise GitHub hosting servers for example)
You will need to subscribe to this webhook.
https://developer.github.com/webhooks/event-payloads/#issues
Webhook payload object
Key Type Description
action string The action that was performed. Can be one of opened, edited, deleted,
pinned, unpinned, closed, reopened, assigned, unassigned, labeled,
unlabeled, locked, unlocked, transferred, milestoned, or demilestoned.
I have an action job which upload the context to other website. The token was set and stored in the secret.MY_TOKEN.
But others who make the pull request also trigger this action job using the token I set.
How to limit the privilege of executing the jobs that only I can run this action job.
fyi my ci.yml as follow:
name: foobar
on: [push, pull_request]
jobs:
upload:
runs-on: ubuntu-latest
steps:
....
- name: execute upload
env:
TOKEN: ${{ secrets.MYTOKEN }}
run:
upl --token ${TOKEN}
I assume there are two security problems here.
The token is printed in log file.
others who can use this private token by trigger action with their own purpose.
Use the github.repository_owner context
https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#github-context
The syntax should be something like:
- if: github.repository_owner == 'owner_name'
There is a new feature which could help, since July 2022:
Differentiating triggering actor from executing actor
Starting next week, workflow re-runs in GitHub Actions will use the initial run’s actor for privilege evaluation.
The actor who triggered the re-run will continue to be displayed in the UI, and can be accessed in a workflow via the triggering_actor field in the GitHub context.
Currently, the privileges (e.g. – secrets, permissions) of a run are derived from the triggering actor.
This poses a challenge in situations where the actor triggering a re-run is different than the original executing actor.
The upcoming change will differentiate the initial executing actor from the triggering actor, enabling the stable execution of re-runs.
For more details see Re-running workflows and jobs.
I don't believe allowing actions to run only for certain users is a native feature.
However, you could simply check the action context actor and exit early if the actor is not the yourself (or the owner of the repo, or whatever condition you'd like).
currently in Netlify you can create aliases of my custom domain normally, but I would like to know if i can add these alias from an API / Programmatically.
Netlify provides documentation on their api including the following:
UPDATE SITE
PATCH /api/v1/sites/{site_id} will let you update some attributes on a site
PUT /api/v1/sites/{site_id} will let you update some attributes on a site
This lets you update a site. Takes all the same parameters as when
creating a site.
When creating a site, you can set the following properties:
name, the name of the site (mysite.netlify.com)
custom_domain, the custom domain of the site (www.example.com)
password, password protect the site
force_ssl, will force SSL on the site if SSL is enabled
domain_aliases, is an array of OTHER hostnames your site has in addition to the custom domain
processing_settings, lets you set the following processing settings: {“css”: {“bundle”: true, “minify”: true}, “js”: {“bundle”: true, “minify”: true}, “html”: {“pretty_urls”: true, “canonical_urls”: true}, “images”: {“optimize”: true}}
repo, lets you configure continuous deployment. It’s a bit complicated to create a repo object so please contact support for guidance if you want to do this.
Based on this, I suspect you would be able to use their API to adjust your custom domain - however they do not make any reference to a means to adjust aliases such that you can control more than one domain at a time. You may be able to contact their support team and request assistance if that is something you require.
We have a custom test runner for our UI Smoke Tests and I want to report code coverage to TeamCity to enable metrics monitoring and failing of build, etc.
I'm trying the use service messages to achieve this as follows:
##teamcity[buildStatisticValue key='CodeCoverageAbsMCovered' value='5']
##teamcity[buildStatisticValue key='CodeCoverageAbsMTotal' value='10']
But it's not being picked up. Can someone please tell me how to send coverage data to Teamcity.
Thanks,
dave
The key used in service messages should not be equal to any of predefined keys.