controllo - #1
Open
virgo075 wants to merge 1254 commits into
Open
Conversation
Owner
Author
|
false profile |
Add 'Git for Teams' to ext book list
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.5 to 1.10.8. **This update includes a security fix.** - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.10.5...v1.10.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
[Security] Bump nokogiri from 1.10.5 to 1.10.8
Bumps [puma](https://github.com/puma/puma) from 3.12.2 to 3.12.3. **This update includes a security fix.** - [Release notes](https://github.com/puma/puma/releases) - [Changelog](https://github.com/puma/puma/blob/master/History.md) - [Commits](puma/puma@v3.12.2...v3.12.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
[Security] Bump puma from 3.12.2 to 3.12.3
Bumps [rake](https://github.com/ruby/rake) from 12.3.2 to 13.0.1. **This update includes a security fix.** - [Release notes](https://github.com/ruby/rake/releases) - [Changelog](https://github.com/ruby/rake/blob/master/History.rdoc) - [Commits](ruby/rake@v12.3.2...v13.0.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
[Security] Bump rake from 12.3.2 to 13.0.1
Bumps [puma](https://github.com/puma/puma) from 3.12.3 to 3.12.4. **This update includes a security fix.** - [Release notes](https://github.com/puma/puma/releases) - [Changelog](https://github.com/puma/puma/blob/master/History.md) - [Commits](puma/puma@v3.12.3...v3.12.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
[Security] Bump puma from 3.12.3 to 3.12.4
manpages: add other languages
trademark policy: spell out US reg#
This is an alternative to #1441, as we don't seem to be using the gem at all. There's no `require 'json'` line, though we do have one call to JSON.generate() for the taglines on the main page. This _seems_ to work anyway, though.
Gemfile: drop json gem
Progit: switch German translation to complete
The regex must include '-' to import zh HANS pages.
Once upon a time this template was used across multiple platforms. But now the only thing it's still serving is mac, so let's make that clear in the filename.
The binary installer we auto-redirect to is often several versions behind. This can be confusing for users who are looking for the latest version. Let's make the situation more clear by describing a few possible options.
The kernel.org directory for tarball is rather long these days. Let's mention the latest version with a direct link to the tar.gz file (just like I recenlty did for the macos page). We could also link to the .xz, which is slightly smaller, but I worry that users may xz-utils installed.
This is much more readable than the manual expansions, and would get any encoding right (on the off chance that the version names had funny characters in them).
We don't reference the project name this way anymore (since it's just one of many options, we just put the URL in with the content).
The list of versions has grown quite long over the years, and it's
almost certain that nobody care about v1.4.3.5 from 2006 these days.
Having a big list creates a few problems:
- it's annoying when setting up a development environment, as we
import a zillion uninteresting tags by default
- the query for "which versions touched this documentation"
is one of the most expensive things we compute on the fly
- the "which versions touched it" list for some manpages has gotten
absurdly long. The one for https://git-scm.com/docs/git scrolls
halfway down the page, and still cuts off at v2.4.1.
Let's put a little manual logic into the import process. We'll omit very
old versions entirely (I chose v2.0 as an arbitrary cutoff). For
somewhat-old ones, we'll import only the most recent point release (so
v2.16.5 but not v2.16.4). For anything v2.17.x and up, we'll continue to
import all releases.
Rubocup prefers that we use 'Enumerable#reverse_each' instead of using each method separately. This improves performance by not requiring '#each' to slurp up the results of reversing the list before enumerating it. Switch out one for the other for a slight performance win, but mostly to get Rubocop happy again.
give alternatives for downloading on macos
Since Rails 5.1, specifying a Rails version for which the migration was written for is required. This commit adds the missing versions.
In `#previous-versions-dropdown footer`.
Use semantic HTML elements for Git version command
Of the `git --version` code snippet.
Add Active Record versions to migrations
Use pseudo element to represent shell prompt
Update Sublime Merge graphics
Add missing columns to schema
Fix typo in comment
For better usability, highlight the active book section with a distinct color for a faster scan.
Highlight active section with the orange color
As of the previous commit, nobody looks at it anymore.
Otherwise we get a complaint that opening a URI through a plain `open` is deprecated (though it still works for now).
- Create pull request template - Prevent contributors opening empty issues - Remove old ISSUE_TEMPLATE file that's no longer needed - Redirect unwanted bug reports with config.yml file - Remove wall of text in templates that used to redirect unwanted stuff - Use clearer headings for operating system/browser section - Use clear language - Capitalize noun Git where it's used - Fix whitespace and file formatting
This tries to clarify why we're sending people to the "community" page for problems with the manpage content.
…ates chore: improve GitHub templates
My main goal here is updating mimemagic, as the version in the lock file got pulled due to a GPL problem. It looks like it has since been resolved, but newer versions of rails use mini_mime instead. So let's just do a full bundle update to pick up the newer rails. This does pick up a few other minor updates, but I don't see any reason not to do so (assuming everything still seems to work).
We use sha1 as a checksum for deciding when pages are out of date (so a weak algorithm is fine). This is really independent of Git's use of sha1, so I think it could just be changed. But it would probably involve a complete re-import of all of the pages. So let's just ignore it for the purposes of this PR.
run "bundle update"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.