Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate git submodule workflow for drush mk #50

Open
1 of 5 tasks
br2490 opened this issue Oct 20, 2017 · 3 comments
Open
1 of 5 tasks

Deprecate git submodule workflow for drush mk #50

br2490 opened this issue Oct 20, 2017 · 3 comments
Labels

Comments

@br2490
Copy link

br2490 commented Oct 20, 2017

  • Started cleanup 1 Nov 17.
  • Create new branch from master
  • Cleanup the new branch by removing submodule structure.
  • Verify final draft of new master branch and push to "master-draft" branch.
  • Ping @patdunlavey
@patdunlavey
Copy link
Collaborator

patdunlavey commented Oct 20, 2017

Notes from our call. (see https://commonmedia.teamworkpm.net/#tasks/14023557?c=6235983)

The problem:

  • Production and dev branches are no longer serving a useful purpose because code bases on prod and dev server boxes have unclean git status and cannot git pull without merge conflicts.
  • Originally depended on git submodules for most (all?) drupal and islandora module management. However this system broke when a vendor used drush to update modules. And, submodules are just hard to work with, even in good circumstances.

The solution we agreed on:

  • Production server will serve as the canonical code base until we can get it to a clean git status.
  • Ben will checkout a new branch on the production server.
  • On this branch he will break apart the code changes into commits with appropriate comments.
  • Once clean, Ben will push this branch back to origin. At this point, it may make sense to set up the master branch as the canonical code base starting from this branch, merge that to production, and checkout the production branch on the production server.
  • Probably working on the dev server, Ben will back out all the git submodules, and commit this code into an appropriate working branch.
  • When merging back to master, we agreed to use pull requests, so that I and/or others can review his changes. Once master is up to date, it can be merged into production, and pulled on the production server.
  • Moving forward, we will use a combination of drush up (for contrib modules and libraries) and drush make (for islandora modules and libraries) to manage code updates. As these updates are performed, they will be committed - preferably on a branch specific to the update task, then move through the workflow of pull request to master.

For now, Ben will shoulder the impetus for most of this work, and I will stand by to assist and advise, as needed.

Thanks!

@MarthaTenney
Copy link
Member

is this complete? could this be a BD project?

@br2490
Copy link
Author

br2490 commented Jan 18, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants