In the GitHub Action documentation, we can use directly a Docker image from DockerHub as an action.

Can we add a new category for this kind of Action? Or just add them to others links in an existing category?

For example, this docker image contains a documentation section to b

Currently, using echo "$DOCKER_PASS" | docker login -u "$DOCKER_USER" --password-stdin produces a warning:

WARNING! Your password will be stored unencrypted in /home/runner/.docker/config.json.
Login Succeeded
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Please, provide an example workfl

It took a few attempts to find a solution to get a version # to tag the releases with. In my case I have a VERSION file containing the version number, such as 0.1.0. This solution should be applicable even if the desired version is stored elsewhere so long as it can be accessed from a bash shell.

The first step gets the version via a run command and sets the output. See the [documentation for

Pain point :
Many of our the analysts are not familiar with using the API for analysis.

Solution:
A google script can easily fetch the data from the API and store it in their personal Google Sheet every 30 minutes or so.
If we can create the script and write a simple document on how to do this, it would be a great help!

When testing in a matrix, uploads often fail after the first one. I'm testing against different versions of Python, and I only need to upload the coverage information once, by including

if: matrix.python-version == 3.8

in the codecov job. It took me a while to figure this out, so maybe it is nice to include this in the readme.

Hi! I can't find any clear documentation about the asset_content_type field -- what the options are, what this does etc.

If there is some documentation in another place, maybe it'd be worth linking to it in the readme?

Sorry if there's been an existing issue for this -- I couldn't find any.

Brett Fox's answer to When VCs say the giants will enter the market and put you out of business in a day, what is the best answer you can give? - Quora





July 19, 2019 at 01:27PM

via Instapaper https://ift.tt/32B5pTS

In #1, it's discussed that the action should be using profiles to prevent stomping on other AWS actions which are used by the repo.

However, in the AWS CLI documentation, it's mentioned that the CLI supports certain environment variables natively. This includes authentication-related variables such as `AWS_ACCESS_KEY

Summary
Documentation for handling nested projects is out of date/incorrect.

The README example for the working-directory option shows that the folder structure below should work with a configuration that sets working-directory: e2e. This is not the case.

File structure:

repo/
  app/
  e2e/
    cypress
    

The ShouldQueue interface is a laravel common to tell the queueable class to queue itself as normal behavior.
It would be great if this packages supports this interface and queues actions called via execute() only if the class implements this interface.

Currently certain PR's coming from forks result in the action running in the context of the fork, which means it can't post a comment or a PR review to the PR/issue.

Possible workarounds:

1. Report the size table back using a Status Check
   • Not sure if GitHub's UI will handle

I missed the Chrome team adding "stack packs" in v5.0. Right now the only additional rules are for WordPress and AMP (and apparently React and Angular soon) but it would be cool to have a configuration flag to add these to the action.

https://github.com/GoogleChrome/lighthouse-stack-packs