| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Similarly to https://github.com/rails/rails/pull/32626/commits/9c3fe52f5fa9904b43bf76be13f85db57c223d0c
|
| |
|
|
|
|
| |
[LinkedRach, Daniel Colson, Xavier Noria]
|
| |
|
|
|
| |
Before we forget...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Code Triage](https://www.codetriage.com/) is an app I've maintained for the past 4-5 years with the intent of getting people involved in open source. It sends subscribers a random open issue for them to help "triage". For Ruby projects such as "rails/rails" you can also subscribe to documentation. For example you can get a few random documented methods, or if you want to write docs, get undocumented methods.
The initial approach was inspired by seeing the work of the small core team spending countless hours asking "what rails version was this in" and "can you give us an example app". The idea is to outsource these small interactions to a huge team of volunteers and let the core team focus on their work.
The purpose of the badge is to give more people an easier way to start contributing to Rails. Here's what it currently looks like:
[![Code Triage Badge](https://www.codetriage.com/rails/rails/badges/users.svg)](https://www.codetriage.com/rails/rails)
The number is how many people are currently subscribed (a.k.a. "helpers") to the project on CodeTriage, the color is based off of the number of open issues in the project. You can see an example of this badge on another popular open source repo [Crystal](github.com/crystal-lang/crystal/).
> For context to non-rails core: I also maintain sprockets (though a release hasn't happened in some time, sorry), and I have commit to Rails. I'm not some rando trying to push arbitrary links to READMEs on GitHub.
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
| |
The first heading in some README's are indicated using a second level
heading (`##`), which in my opinion is of incorrect structure.
Therefore, in this patch I changed the first heading to a first level
heading (`#`) in README's where this incorrect structure occurs.
[ci skip]
|
| |
|
|
|
|
|
|
|
| |
A couple of the READMEs were still referring the old welcome page. This
is a small change that goes over it.
[ci skip]
|
|
|
|
| |
[ci skip] Link to actioncable/README.md for more details
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Add ActiveJob to "Welcome to Rails" section
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
|
|
|
| |
A link to the README of each module is included in "Welcome to Rails",
only ActiveModel (and ActiveJob, see #17264) are missing.
[ci skip]
|
|
|
| |
Ruby on Rails Tutorial link updated.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The rails/rails gemnasium page (https://gemnasium.com/rails/rails) is not helping much.
It lists 0 dependencies so there is not much to track. Also our gems mostly depend
on other gems we control. There is not much point in monitoring them.
The batch was introduced with #3909.
|
|
|
|
|
| |
This has no effect on the API docs. The main API page is taken from:
railties/RDOC_MAIN.rdoc
|
| |
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating the global Rails README following work by @strzalek et al which extracted Action View to a separate gem, and also some other improvements.
Summary of changes:
* Reordered the paragraphs from View-Model-Controller to Model-Controller-View, based on how (IMHO) most people think about the structure and hierarchy of the framework and their code in it.
* Added references to ActionView's README in the _View_ paragraph
* Reworded the _Controller_ paragraph to briefly mentioned routing as handled by Action Dispatch, and that both Action Dispatch and Action Controller work together to form the request-handling Action Pack
* Removed paragraph saying Action Pack is coupled with Action View, as this is no longer the case
* Added brief references to Action Mailer and Active Support, since they are both major Rails components. Briefly mentioned in the _View_ paragraph that Action View is often used to generate the body of the email, in addition to the other typical of using to build a response body.
|
|
|
| |
links were redirects
|
| |
|
| |
|
|
We tend to use Markdown for everything but the API, the
README is no longer used as the home page of the API
after 7a5aa72, so we can now migrate it.
|