-
Notifications
You must be signed in to change notification settings - Fork 228
Git Workflow
Joshua Buker edited this page Sep 27, 2016
·
3 revisions
- Fork Sorcery on Github
- Clone your forked copy onto your working machine
- Open terminal and
cd
into where you would like the repository saved. - Run the clone command, example:
git clone https://github.com/<your_user_name>/sorcery.git
- With the same terminal,
cd
into your freshly made repository using:cd ./sorcery
- Add upstream to remotes
git remote add upstream https://github.com/Sorcery/sorcery.git
- Run
bundle install
- To ensure everything is ready, run
bundle exec rspec spec
, all tests should pass.
- Make your changes, adding additional specs if you are adding functionality.
- Run
bundle exec rspec spec
to ensure your changes didn't break other functionality. -
git commit
with a relevant message - Pull down any updates
git pull --rebase upstream master
- If there are any conflicts, resolve them via text editor then run:
*
git add -A
thengit rebase --continue
git push --force-with-lease
- (WARNING: This will delete any history on your github fork and overwrite it with your local copy. This is necessary however if history was rewritten due to changes to the main repository.)
- Submit a pull-request via github.
This page is a work in progress; if you have any suggestions or see any mistakes, please update the page as needed!
Meta
Using Sorcery
- Activity Logging
- Brute Force Protection
- DataMapper Support
- DelayedJob Integration
- Distinguish login failure reasons
- External
- External---Microsoft-Graph-authentication
- Fetching Currently Active Users
- HTTP Basic Auth
- Integration Testing
- OAuth Landing Page
- Password-less Activation
- Remember Me
- Reset Password
- Routes Constraints
- Session Timeout
- Simple Password Authentication
- Single Table Inheritance Support
- Testing Rails
- User Activation
Contributing to Sorcery