As we are getting Composer 2.0 closer and closer to a stable release,
and would like to get more people involved with testing it, it is
quite important to get the most common plugins to support our 2.0
branch. Otherwise many users will not be able to try the latest
Composer snapshots when we switch them to 2.0.

If you maintain a Composer plugin and would like to help, here is how:

• Get

There is a bad link on the master branch readme (https://github.com/golang/dep/blob/master/README.md) in the section for Windows users looking to download dep.

The link is bolded in this sentence below and currently points to https://go.equinox.io/github.com/golang/dep/cmd/dep which returns a 404 code

• On Windows, you can download a tarball from go.equinox.io.

• I've read and understood the CONTRIBUTING guidelines and have done my best effort to follow.

Report

What did you do?

• enabled generate_multiple_pod_projects in Podfile

What did you expect to happen?

• correctly migrate targets to separate projects, build project then

What happened instead?

The documentation does not provide a simple things we can follow from start to finish.

The introduction section is really "installation", and go quiet deep in the different option to install the tools.

Quick Start

# install poetry
curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python
# Creating a new project
poetry new poetry-demo
# Add a de

I have a project that is in a monorepo and uses yarn right now.

I'm considering migrating to pnpm for the monorepo, as well as all other projects I contribute to, as I have a small SSD as local storage (and with Windows...). However, it would be ideal if there was compatibility between yarn's workspaces and pnpm, so that we don't have to jump "all in" to it.

To this end, yarn allows packages

I was trying to install. And it wouldn't install. Was stuck for a long time till I scrolled down and found the requirements.

Background: I have a pull request into a repository where the npm module isn't up-to-date with master, and I'd like to test out my branch in a module that depends on it through a bunch of different deep dependencies. It seems like patch-package would be a great solution for this.

Problem: When I append .patch to my GitHub URL it gives me a patch, but when I pass it to patch -p1 it

Is your feature request related to a problem? Please describe.

Not related to a problem

Describe the solution you'd like

We opened #808 to discuss how we might use GitHub actions. At the time, this repo didn't have actions enabled. Now that it does, we should try them out for some of the things in that thread.

_Edit from @arschles - we have focused this issue to just the twitte

What Renovate type are you using?

I am using Renovate in a private project hosted on Gitlab.com

Describe the bug

It's not a bug but a simple typo. If you start using Renovate, it will usually create a "Pin dependencies" pull request. The PR template contains a

Mint could support installing man-pages.

To support this, mint install need to

• require the project to have man-pages under a specific directory like docs/man to install man-pages.
• provide an option to support other location. e.g. [git's homebrew formula downloads man-pages from other location than it's main repo](https://github.com/Homebrew/homebrew-core/blob/master/Formula/git.rb#L

There is a ton of documentation here and that's great, however, the first introduction to this tool is overwhelming and should be simplified. You may want to move some of the more stable documentation to the Wiki and reference it from the ReadMe.

Report

What did you do?

• run pod install on an empty folder with just this Podfile

platform :ios, '8.0'

plugin 'cocoapods-rome'

target 'caesar' do
  pod 'Alamofire'
end

• What did you expect to happen?
  To get an output folder with the compiled Alamofire framework

• What happened instead?
  Got the SWIFT_VERSION missing error.

Command

When you run original bower update it quietly installs all required components including those never installed before.

bowerphp exits with error:

  [RuntimeException]
  Package adminlte is not installed.

Usually package managers (bower, npm, composer, ...) do install when you run update.

The options should_remove_source_branch and merge_when_pipeline_succeeds are parsed from the configfile.

https://github.com/pyupio/pyup/blob/8178ca204ebbac71d94198e8a4ef89e828ef0908/pyup/config.py#L163

I can’t find anything about them (or any gitlab-specific config-options) in the documentation.

Hi,

It's possible that I'm just misunderstanding the documentation here, but in the docs it says that using the --test flag on the build command wil make cget "try to run the check target" after building.

Does this mean that it will try to execute the resulting executable that is generated from building the check target? If so, this does not seem to happen.

Or am I misunderstand

It should be possible to add a module defining the following, all in the add command,

• sources
• dependencies
• binaries
• parameters
• environment variables
• resources
  as they all have different parameter keys.

Currently build agents run mbt version command at the end of the build. We should add a smoke test for each command (mbt describe | build | apply) to this list for release builds.