Skip to content
This repository was archived by the owner on Jan 2, 2026. It is now read-only.

Commit 10d4511

Browse files
committed
Add GitHub documents
1 parent 7c43c7b commit 10d4511

File tree

4 files changed

+98
-0
lines changed

4 files changed

+98
-0
lines changed

.github/CONTRIBUTING.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Contribute To Genesis JS / No JS
2+
3+
Community-made patches, localisations, bug reports and contributions are very welcome and help make Genesis JS / No JS the best plugin for styling Genesis child themes depending whether JavaScript is enabled or not.
4+
5+
When contributing please ensure you follow the guidelines below so that we can keep on top of things.
6+
7+
## Getting Started
8+
9+
- Submit a ticket for your issue, assuming one does not already exist.
10+
- Raise it on our [Issue Tracker](https://github.com/GaryJones/genesis-js-no-js/issues).
11+
- Clearly describe the issue including steps to reproduce the bug.
12+
- Make sure you fill in the earliest version that you know has the issue as well as the version of WordPress you're using.
13+
14+
## Making Changes
15+
16+
- Fork the repository on GitHub.
17+
- Make the changes to your forked repository.
18+
- Add unit / integration tests where necessary.
19+
- Ensure you stick to the [WordPress Coding Standards](http://codex.wordpress.org/WordPress_Coding_Standards) and have properly documented any new functions.
20+
- When committing, reference your issue (if present) and include a note about the fix.
21+
- Push the changes to your fork and submit a pull request to the 'develop' branch of the ... repository.
22+
23+
## Code Documentation
24+
25+
- Please make sure that every method is documented well and the documentation follows the standards.
26+
27+
At this point you're waiting on us to merge your pull request. We'll review all pull requests, and make suggestions and changes if necessary.
28+
29+
# Additional Resources
30+
- [General GitHub Documentation](http://help.github.com/)
31+
- [GitHub Pull Request documentation](http://help.github.com/send-pull-requests/)

.github/ISSUE_TEMPLATE.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
<!--- Provide a general summary of the issue in the Title above -->
2+
3+
## Expected Behavior
4+
<!--- If you're describing a bug, tell us what should happen -->
5+
<!--- If you're suggesting a change/improvement, tell us how it should work -->
6+
7+
## Current Behavior
8+
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
9+
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
10+
11+
## Possible Solution
12+
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
13+
<!--- or ideas how to implement the addition or change -->
14+
15+
## Steps to Reproduce (for bugs)
16+
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
17+
<!--- reproduce this bug. Include code to reproduce, if relevant -->
18+
1.
19+
2.
20+
3.
21+
4.
22+
23+
## Context
24+
<!--- How has this issue affected you? What are you trying to accomplish? -->
25+
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
26+
27+
## Your Environment
28+
<!--- Include as many relevant details about the environment you experienced the bug in -->
29+
- Version used:
30+
- WordPress version:
31+
- Genesis version:
32+
- Base child theme:
33+
- Link to your project:

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
<!--- Provide a general summary of your changes in the Title above -->
2+
3+
## Description
4+
<!--- Describe your changes in detail -->
5+
6+
## Motivation and Context
7+
<!--- Why is this change required? What problem does it solve? -->
8+
<!--- If it fixes an open issue, please link to the issue here. -->
9+
10+
## How Has This Been Tested?
11+
<!--- Please describe in detail how you tested your changes. -->
12+
<!--- Include details of your testing environment, and the tests you ran to -->
13+
<!--- see how your change affects other areas of the code, etc. -->
14+
15+
## Screenshots (if appropriate):
16+
17+
## Types of changes
18+
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
19+
- [ ] Bug fix (non-breaking change which fixes an issue)
20+
- [ ] New feature (non-breaking change which adds functionality)
21+
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
22+
23+
## Checklist:
24+
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
25+
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
26+
- [ ] My code follows the code style of this project.
27+
- [ ] My change requires a change to the documentation.
28+
- [ ] I have updated the documentation accordingly.
29+
- [ ] I have read the [CONTRIBUTING] document.

.github/SUPPORT.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Support for Genesis JS / No JS
2+
3+
The best place to get support for this project is on the [Issue Tracker](https://github.com/GaryJones/genesis-js-no-js/issues).
4+
5+
You can also find Gary on WordPress Slack, and [Twitter](https://twitter.com/GaryJ), though they may not be as easy to communicate the problem compared to the Issue tracker.

0 commit comments

Comments
 (0)