- Notifications
You must be signed in to change notification settings - Fork10
reactstrap/reactstrap.github.io
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
If you have found an issue or would like to request a new feature, simply create a new issue detailing the request. We also welcome pull requests. See below for information on getting started with development and submitting pull requests.
If you find a bug in the source code or a mistake in the documentation, you can help us bysubmitting an issue to ourGitHub Repository. Even better you can submit a Pull Requestwith a fix.
Please see the Submission Guidelines below.
You can request a new feature by submitting an issue to ourGitHub Repository. If youwould like to implement a new feature then consider what kind of change it is:
- Major Changes that you wish to contribute to the project should be discussed first in aGitHub Issue orSlack so that we can better coordinate our efforts, preventduplication of work, and help you to craft the change so that it is successfully accepted into theproject. Slack invites can be obtainedhere.
- Small Changes can be crafted and submitted to theGitHub Repository as a Pull Request.
If you wish to submit a pull request for a new feature or issue, you should start by forking this repository first. After you have forked and cloned the repository locally, create a new branch with a name that loosely describes the issue on which you will be working. Once you think you have the addressed the issue in question, submit a pull request. Here are some guidelines to follow when writing code for reactstrap:
- Commit messages should follow Angular'sGit Commit Guidelines.
- Intermediate and work-in-progress commits should be rebased out.
- Keep pull requests tightly scoped to the issue or feature being addressed.
- All changes from every developer must go through code review before they will be merged.
- All changes must pass the CI build. Travis CI will automatically update your PR with the build status.
- All changes must have unit tests.
- All components must have a demo implementation in the
docs/lib/examplesdirectory.
About
Contributing
Security policy
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Contributors2
Uh oh!
There was an error while loading.Please reload this page.