| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
7462: Document running tests in parallel inside a dev environment r=deivid-rodriguez a=colby-swandale
### What was the end-user problem that led to this PR?
We do not have any documentation for running the test suite in parallel. Developers working on Bundler may be unaware that the test suite can be executed in parallel to help speed up the time needed to run tests.
### What is your fix for the problem, implemented in this PR?
Document how to run the parallel Bundler test suit in the Contributing docs.
Co-authored-by: Colby Swandale <me@colby.fyi>
(cherry picked from commit fe91eb21cfc07e4fb5710126302d58b433c6d734)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
7355: Restore version bumping to `release:prepare_patch` r=deivid-rodriguez a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was that I removed too much code in #7350.
### What was your diagnosis of the problem?
My diagnosis was that since I removed the auto-bumping `version.rb`, the task no longer works before it tries to cherry-pick changes for the _current_, not the _to be released_ version, so I fails because it finds no open PR for that milestone (because it's already been released).
### What is your fix for the problem, implemented in this PR?
My fix is to restore the code that automatically bumps the version to the next patch level version, and commits that to the release branch.
### Why did you choose this fix out of the possible options?
I chose this fix because it works for me.
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
(cherry picked from commit 89b120310fa853ef7980fa7d78a2c61ae3acf9d6)
|
|
|
|
|
| |
The first prerelease of a bundler minor series is usually `.pre.1`, not
`.pre.0`.
|
|
|
|
|
| |
The bundler-changelog repo has not been used for a long time. Let's
update the playbook to not mention it.
|
| |
|
|
|
|
| |
And use single quotes consistenly.
|
|
|
|
|
|
|
|
| |
The current numbers are misleading and coverage tracking doesn't work in
most of the places since the current test suite is mostly based on
spawning subprocesses, and coverage doesn't get properly tracked there.
Let's revisit this in the future.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Add a POLICIES document
This isn't intended to be authoritative, but it's a start!
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
The links to bundler.io were leading to a 404 error in GitHub because the full URL hadn't been written out.
|
| |
| |
| | |
Per @hmistry's suggestions, I've moved the development instructions outside of the bulleted list and made it its own sentence. And I've shortened the copy under the "Contributing to Bundler" header.
|
|/
|
|
|
| |
Hey team,
As part of an ongoing effort to revamp the docs, I've been working with @indirect to rewrite the contributor guidelines README. We wanted to streamline the way the information was laid out, and make it more explicit to potential contributors how they can contribute and what next steps they needed to take. We condensed everything down to three sections (a general guidelines section, contributor section, and a new, supporting Bundler section). Everything links out to existing documentation.
|
|
|
| |
Github has defined a couple of tags to use for classifying issues that are suitable for new contributors to fix/contribute towards. We have started using these tags in Github so we should start linking to them in our documentation as well.
|
|
|
| |
We added this requirement before the changelog was automated. Now that the changelog generated by a script, it's not helpful for PRs to update the changelog anymore, so we shouldn't expect it anymore.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
improve development setup docs and remove redundant quotes
### What was the end-user problem that led to this PR?
Some distrobutions of linux do not ship with the `col` command which `ronn` requires. And there are also some code blocks that don't need to quoted.
### What is your fix for the problem, implemented in this PR?
Update the developer docs to include instruction to install the package that has the `col` command and remove the code block quotes that don't need to be there.
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Hey @indirect @segiddins,
I've implemented the suggested updates that @arbonap provided. Specifically, adding a new step 1, and adding instructions for creating aliases in bash.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Fix markdown headers in doc/development/readme
GH now requires a space between `#` and the header
|
| | |
|
|/
|
| |
Fixed "Writing" heading and converted "here" into links for clarity
|
|
|
|
| |
used relative path instead of full url
|
| |
|
| |
|