✏️ Editing: page-making_changes_to_ruby_md.ri Read Only

U:RDoc::TopLevel[	i�I"+contributing/making_changes_to_ruby.md:ETcRDoc::Parser::Markdowno:RDoc::Markup::Document:@parts[S:RDoc::Markup::Heading:
leveli:	textI" Contributing a pull request;TS;	;
i;I"Code style;To:RDoc::Markup::Paragraph;[I"RHere are some general rules to follow when writing Ruby and C code for CRuby:;To:RDoc::Markup::List:
@type:BULLET:@items[
o:RDoc::Markup::ListItem:@label0;[o;;[I"NDo not change code unrelated to your pull request (including style fixes);To;;0;[o;;[I"dIndent 4 spaces for C without tabs (tabs are two levels of indentation, equivalent to 8 spaces);To;;0;[o;;[I"*Indent 2 spaces for Ruby without tabs;To;;0;[o;;[I"+ANSI C style for function declarations;To;;0;[o;;[I"Follow C99 Standard;To;;0;[o;;[I"'PascalStyle for class/module names;To;;0;[o;;[I"8UNDERSCORE_SEPARATED_UPPER_CASE for other constants;To;;0;[o;;[I"+Abbreviations should be all upper case;TS;	;
i;I"Commit messages;To;;[I"1Use the following style for commit messages:;To;
;;;[o;;0;[o;;[I" Use a succinct subject line;To;;0;[o;;[I"hInclude reasoning behind the change in the commit message, focusing on why the change is being made;To;;0;[o;;[I"�Refer to issue (such as <code>Fixes [Bug #1234]</code> or <code>Implements [Feature #3456]</code>), or discussion on the mailing list (such as [ruby-core:12345]);TS;	;
i;I"CI;To;;[I"2GitHub actions will run on each pull request.;To;;[I"�There is {a CI that runs on master}[https://rubyci.org/]. It has broad coverage of different systems and architectures, such as Solaris SPARC and macOS.;T:
@file@:0@omit_headings_from_table_of_contents_below0

📁 File Manager Pro

📁 File Manager Pro