Switched rails/rails#37485 to use assert_changes but it tries to circumvent minitest's assert_equal nil, after deprecation warning by using assert sidestepping minitest's diffing. So instead it spews out a massive amount of text which makes it hard to find where the change was.

We should probably revert rails/rails@bbe437f

Motivation

I think you are missing an important piece of information in Collections documentation

Suggestion

Add a note that if the file does not have a Front Matter defined, it will not be registered by Jekyll custom collections.

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read [docs.fastlane.tools](https:/

A detailed description of the proposed feature

Provide an easy way to change brew's origin setting so people can use other source than github.

brew --config
HOMEBREW_VERSION: 2.1.15
ORIGIN: https://github.com/Homebrew/brew // easy way to change this  
HEAD: 2bf8015bc44878d432fb9da4f11e1d8abcef8f32
Last commit: 6 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core 

Current Vagrant documentation doesn't provide example of using netmask option when you want to configure IPv4 interfaces (only IPv6).

I would like to improve docs on this part to avoid confusion between IPv6 netmask (example: "64") and IPv4 netmask (example "255.255.255.0"): https://github.com/hashicorp/vagrant/blob/b886ec

This is in response to #7264, since we decided that PR is not the right way to do it.

I think we decided on: move the non-browser-specific tests out of the browser-specific test files.

So if the "chrome only" tests pass when using Firefox for instance, they should be moved to unit tests or into a common spec file of some kind.

Hi,

I am playing around a little with results of /contacs and the like.

When I send a well formed request to /aspect_memberships it usually returns something like

Content-Type:"application/json; charset=utf-8"

{"id":9833,"aspect":{"id":9989,"name":"aspects name"}}

(I don't know what 9833 is but 9989 is the aspects ID)

If I log out or did the authentication wrong or something l

So it seems there is a variable current_path which points to wherever :deploy:to/current symlink points. So after deploy:symlink:release it points to the current release.
Also there is a variable release_path that seems to point to the current release directory which is created by create_release task.

What

The Readme is our comprehensive sinatra documentation and deserves a lot of love. Thank you for everybody who has contributed to it so far!

The translations are great but some of them seem incomplete or outdated. For sinatra 2.0 they need a major overhaul and here's a list of languages that need to be worked on:

• German
• Spanish
• French
• Hungarian
• Portuguese (Br

If the JSON configuration for allowed runtime reflection contains a class that is not on the class path, the tool tells me to verify that my configuration matches the schema:

error: Error parsing reflection configuration in /home/dsyer/dev/scratch/graal/reflect.json:
Class no.such.Object not found
Verify that the configuration matches the schema described in the -H:PrintFlags=+ output fo

Expected behavior

When I have keys and values of a Hash aligned I should not see this offense in Rubocop report.

Actual behavior

Gist with larger example hash: https://gist.github.com/roolo/580b5061003355e07f631cffbe2fea9c

user:         current_user,
subscription: FactoryBot.create(:subscription,

When I have hash like this, I am told I should _elements of a hash

This is not really a bug with Spree, more of an issue with image caching and using a CDN for images served through Rails 5.2 Active Storage, but I figured it might be useful to have a documented solution on this issue for other Spree users.

Issue

Active Storage is simple to set up and get working, but offers no out of the box solution for serving your public facing images through a content

Expected behavior

If I go to the documentation site, and I see a feature documented, I should be able to use it or at least be informed about the series it was (or will be released).

Actual behavior

Features are documented in the website as soon as the land into master, but the release cycle is much slower.

How to reproduce

See #5497 for an example.