Both GitHub and GitLab offer their own public Docker Registry:
https://github.com/features/packages
https://docs.gitlab.com/ee/user/packages/container_registry/

Gitea doesn't seem offer one yet.

Describe the solution you'd like

It would be great if GoReleaser could just automatically authenticate with the given registry on hostname/im

I cannot figure out how to use properly danger on circleci 2.0 with workflows

Support I have a linear workflow where I bundle my app / install libraries (build job) and then run the tests in parallel. (I'm taking Ruby/Rspec as an example).

How can I execute Danger to report test failures on all containers ?

Currently if a job fails on circleCI, the dependent jobs are not ran (ie if I

The GitHub Integration just fails with a GitHub Error Response if your Issue Comment gets too long.

It’d be great if we truncated the message, & added a [truncated] 📝?

Thoughts @orta ? I’m happy to implement this if you have advice!

Hello,

I would love to see some instructions on how to get this generated file/folder structure skeleton to work well with google/clasp's set up, specifically where to place its .clasp.json, appsscript.json, etc, relative to the src folder of typescript-library-starter, so that clasp push would work perfectly.

TIA, and good work!

extend the docs on how the bot can be used with GitHubActions.

GithubActions is a neat and fast new way to interact with githubs, its worksflows etc.
its much more powerfull then the regular CI systems we are used to.

this would make it possible to add things like "trigger the lighthousebot via a keyword in a comment" or similar

Per the tox documentation is mentions that the parallel_show_output setting is a global [tox] setting however this doesn't seem to be the case, i.e., if one's tox.ini file is of the form:

[tox]
parallel_show_output = true

then running tox --parallel auto does not show any output.

According to t

This Issue serves as documentation for anticipated breaking changes in 3.0 and allows community feedback to drive the development process.

Breaking Changes 💔

• Do not re-export React from reactn. Have users just import React and ReactN Component/hooks from separate packages. This will help with the namespace conflicts with Component in TypeScript.
• Remove support for @reactn decora

I would love to see a short section about the error codes of check.

Black (under Command line options) does that and it helped me a lot:

--check                     Don't write the files back, just return the
                              status.  Return code 0 means nothing would
                              change.  Return code 1 means some fi

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

With the browserify command, all gets bundled and in case of an error, it does not point to the correct line number of the source code. Is there a trick to make this happen?

Support Netlify

Documentation: https://docs.netlify.com/configure-builds/environment-variables/#git-metadata

Environment variables:

• service detection: NETLIFY
• Branch: BRANCH
• Commit sha: COMMIT_REF
• Is Pull request: PULL_R

https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html#_special_requirements

PID and CAP_ADD options are ignored as they are not yet available in swarm mode. Might be available in mid 2019

After running gem install travis, you need to run another step if you use travis-ci.com instead of travis-ci.org (which is being deprecated). The step is:

travis endpoint --pro --set-default

Background (no need to mention this in the docs): this updates the local config at ~/.travis/config.yml and ensures the travis CLI is uploading the environment secrets to the .com