allow cross-development across forks #105
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CHANGES:
NOTES:
pre-processing config.yml is inconsequential if config.yml contains no erb - i added this to allow peer4commit and tip4commit to co-exist functionally in the same repo - without this functionality, the config.yml would either need to be commited to the repo or manually restored upon each branch change - so i figured this was the least intrusive option
allow peer4commit and tip4commit to co-exist functionally in the same repo - without this functionality one would need to manually swap config files when switching forks
im not sure why the schema was modified - this was not my doing - there must had been some manual additions to the migration files after the initial migrations (notably the email index in the users table)
the addition to .gitignore is o/c also inconsequential - it merely allows peer4commit and tip4commit to co-exist functionally in the same repo
this is the equivelant for this repo of a similar commit to the tip4commit fork