This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1k
Contributing to Fuel UX
Stephen James edited this page Apr 24, 2014
·
16 revisions
- Before writing code, we suggest you search for issues or create a new one to confirm where your contribution fits into our roadmap.
- Fork the Fuel UX repo GitHub help
- Make your changes, being sure to add unit tests for new or changed functionality
- Run the appropriate grunt tasks lint and test your changes (see the Gruntfile.js for tasks, see our style guide for lint errors/warnings)
- Update your fork with the latest code from Fuel UX, merging as necessary
- Commit your changes. We suggest only committing the files within the
js/folder for simpler merging, but you'll want to run 'grunt' after commiting to build the files for any local testing. - If your work is not already in a single commit, rebase and squash into a single commit
- Push to your GitHub repo, using --force if you have rebased
- Submit a pull request to the latest working branch. For help, see GitHub help
- If you're editing something on version 3.1.0, then the branch you submit your pull request to would be 3.1.1 (if your changes are bug fixes).
- If you're planning on making major or minor changes, please contact the maintainers (@kevinparkerson, @interactivellama, or @vernak2539) and they will help you get the proper working branch created.
The Bootstrap repo contained an excellent writeup on the design and thinking that went into building Bootstrap controls. Fuel UX follows this same philosophy. Click the link below to read about it.