Motivation

I have a site where the staging location has a site.baseurl and the live version has not. While working with inline images I found - by looking at the mmistakes codebase, could not discover instruction in the docs - that instead of this:

Mission Statement
Before anything else, I've found a fix to my nokogiri installation problems. I just wanted to submit this issue to update the documentation to help others who might run into this specific installation problem.

I'm running a fresh install of Ubuntu 18.04 and was in the process of setting up my dev enviroment. When I tried to gem install nokogiri it failed, even after fol

After facing an issue caused by Ransack interpreting 1/'t' as true and some unsuccessful research, I found about the sanitize args and the recommended way to skip them. The documentation never mentions that ransackable_scopes_sanitize_args must be a class method and the example shown defines an instance method.

I think that's worth a documentation update, making more clear how to use th

https://github.com/shakacode/react_on_rails/blob/master/docs/basics/recommended-project-structure.md

Instead, let's consider recommending leaving package.json and node_modules at the top-level...

There are no big advantages of having this be inside of the /client directory and there are a few additional bits of unnecessary complexity.

@ashgaliyev please add to this discussion.

In the policy definition below description has an embedded newline and the generated terraform is invalid.

resource "aws_iam_policy" "my_policy_name_role" {
    name        = "my_policy_name_role"
    path        = "/"
    description = "This is the first line of the description followed by a newline
This is on a separate line"
    policy      = <<POLICY
[policy truncated for brevity

Before submitting an issue, please be sure to

• Read the contributing instructions
• Update to the latest Gem version (run bundle update github-pages)

This issue affects

• The site generated by GitHub Pages
• Building sites locally

What did you

I ran into a situation where there was a stupid mistake in one of our cron and we didn't notice it.

I believe we do parse crons already in app to queue jobs in time. So why not complain if some crons contain errors, i.e are not parse-able. I believe they are silently ignore as of now.

If i can get some guidance i will be happy to contribute this. We may add a configuration to raise exception

If this is how we search for a user by username:

Gitlab.users(username: "someuser")

How can we search by user email address?

The Gitlab API documentation says:

You can also search for users by name or primary email using ?search=. For example. /users?search=John.

Does this gem support it?

Related to #529

when you navigate to another page example "About" the menu feels like it is closed too fast and without progressive transition

Example https://github.com/ArturKovacs/emulsion/blob/2f5b5dbadf1f10592367300f7d18f3ffb2bed628/LICENSE.txt

$ bundle exec licensee diff https://github.com/ArturKovacs/emulsion --license mit
Comparing to MIT License:
Input Length:      1074
License length:    1020
Similarity:      94.85%
diff --git a/LICENSE b/LICENSE
index 0ce42af..b81d9df 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,14