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

Documentation:
https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on

Yaml that duplicates error:

name: Test
on:
  push:
    branches:
      - master
jobs:
  build:
    runs-on: [self-hosted, windows]
    name: Test

    steps:
      - name: Ensure Docker is running
        run: |
          docker ps -a

Error received:

Points to cover:

• playbook for how to get started with testing
• differences between testing locally vs staging vs production
• how to configure tests for different environments

@johngrimsey thank you for the idea! Please feel free to comment if I missed something.

Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)

Nice to have check for none production URLs (preview). Netlify has this feature, it just builds user site against branch/PR user/collaborator pushed. Then user sees perf results for the new changes in PR using the same action.

PoC PR - #30

Main problem is race conditions: Netlify can deploy longer then action

Is it possible to pass options to the ssh command?
I couldn't find it in the documentation.

For example how we pass it via ssh -o StrictHostKeyChecking=no

⚠️ Is your feature request related to a problem? Please describe

Add support for code coverage

💡 Describe the solution you'd like

Ideally we could setup jacoco + codecov to have an automated test report after every push/pr.

🤚 Do you want to develop this feature yourself?

• Yes
• No

This feature is up for grab

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

This can be admittedly confusing to users that aren't aware of GitHib releases constraints.

Let's setup some documentation and align with the way Travis deals with tag constraints for cases where users wish to tag on commit pushes https://docs.travis-ci.com/user/deployment/releases/#setting-the-tag-at-deployment-time

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

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.