-
Notifications
You must be signed in to change notification settings - Fork 23
Create Contributor Manual Template #6
Comments
One of the key parts of this template should be "how to build the latest code". We often ask for feedback, but without this guide, people often feel stuck waiting around for a release. If we want feedback, we need to help them understand how to try the lastest code. The steps vary depending on the the module. |
@mojavelinux Would these be the same instructions you provided here asciidoctor/asciidoctor#460 (comment) and/or using a pre-release gem? |
That's one way. The other way is to git clone the project (or download the
That builds the gem and installs it without using the remote RubyGems The final way, which I use hundreds of times a day is to invoke the
The asciidoctor command knows how to find the libraries inside the same Also, tests can be run using:
A single test file can be run using:
(That's a capital "i" as in "include" followed by a lowercase "lib" as in |
I think even describing how docs contributors should name their PRs (Issue-123) and suggesting how they use These may be reflex actions to most experienced git users, but folks who are perhaps using Asciidoctor as their first Open Source GitHub foray may find this type of guidance invaluable. |
I agree (and I have no doubt Sarah does too) that being explicit is good. Like giving driving directions, choose big landmarks instead of subtle clues that are hard to detect. |
This is now a duplicate of asciidoctor/asciidoctor-community-docs#2. |
Produce template covering contribution guidelines and conventions for all aspects of the Asciidoctor project including:
The text was updated successfully, but these errors were encountered: