Drupal
  • Managing Successful Drupal Based Projects
  • Process
    • Team Roles and Responsibilities
    • Ceremonies
    • User Stories Best Practices
    • Glossary
  • Development Resources
    • Coding Standards
    • Setup Local Development Enviornment
    • Content Modeling
    • Git, Commit Messages & Pull Request Guidelines
    • Useful Terminal Commands
    • Package management - Composer, BLT and CI
    • Behat
      • How Behat is used in Acquia Projects?
    • Maintaining your platform/patches
  • JIRA Ticket Templates
    • Ticket Template
    • Composer Updates
    • Redirect endpoints that should not be public
    • Bug Template
    • Sync local with latest upstream code and database sprint X
    • Drupal Enablement
  • ACE & ACSF
    • Deploying to Acquia Cloud
    • ACSF - First Pull Request
    • ACSF & Drupal and Your Platform
Powered by GitBook
On this page
  • User Story:
  • Acceptance Criteria:
  • Implementation Details
  • Description

Was this helpful?

  1. JIRA Ticket Templates

Sync local with latest upstream code and database sprint X

User Story:

As a developer, I want my local to be synced with the latest upstream development branch so that I am ready to work on a ticket as needed.

Acceptance Criteria:

() there is a screenshot of your terminal in the comments of this ticket of the following commands () git fetch --all () git pull upstream develop () git reset --hard upstream/develop (if you have already pulled develop you will need to reset it) () git checkout develop () git push origin develop () composer install () vagrant ssh () blt setup () blt sync:refresh

Implementation Details

run the commands listed above in the AC.

Description

Each developer needs to do this ticket minimum once per sprint.

No test steps. nothing to commit.

PreviousBug TemplateNextDrupal Enablement

Last updated 6 years ago

Was this helpful?