@Snugug shared a cool Github Actions pattern he's using to run multiple jobs in parallel but only after the project has been built. Basically it's a combo of the needs job property combined with uploading/downloading artifacts.

it gives two benefits:

1. you can do jobs in parallel, to get all

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

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.

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
    

Our Markdown in src/pages/docs should not contain tags without any .

In order to increase accessibility those tags should all be changed to Markdown images with alt tags:

[](https://assets.postman.com/postman-docs/.png)

See https://github.com/rust-lang/rustfmt

I have one feature request :)

Right now, when workflow adds a new issue into the column, it's on the top. But for my perspective columns are ordered often by priority and this logic brakes it all.

It is possible to change it and add a cart to the bottom?
On REST API it's really easy https://developer.github.com/v3/projects/cards/#parameters-3 position: bottom not sure about GraphQL.

D