Index
A
- access control
- access models, Access Models-Custom Access Models
- account creation
- add command, Summary, Command Reference
- Aerobatic Hosting, Extending Bitbucket with Atlassian Connect
- Agile environment, The People on Your Team, Evolving Workflows
- Android, Software for Code Reviews
- Ansible, The People on Your Team
- antisocial coding, Project Governance for Nonpublic Projects
- Apache, Distribution Licenses, Leadership Models
- Apache License, Distribution Licenses
- Apache Software Foundation, Software for Code Reviews
- Asana, Administrative Dashboard
- Atlas, Collaborating on Nonsoftware Projects, Trusted Developers with No Peer Review
- Atlassian, Limiting Access with Protected Branches
- Atlassian Connect, Extending Bitbucket with Atlassian Connect
- automated gatekeepers, Types of Reviewers
- automated self-check, Types of Reviews
B
- backward compatibility (see semantic versioning)
- ball-and-chain diagrams, Mainline Branch Development
- Balsamiq, Documenting Your Process
- Benevolent Dictator For Life (BDFL) governance model, Leadership Models
- benevolent dictators, Types of Reviewers
- BFG Repo Cleaner, Really Removing History
- bisect command, Historical Reenactment with bisect-Historical Reenactment with bisect
- bisect inefficiencies, Undoing Shared History
- Bitbucket, Really Removing History
- access control in, Access Control-Limiting Access with Protected Branches
- account creation for, Creating an Account-Creating an Account
- and Atlassian Connect, Extending Bitbucket with Atlassian Connect
- creating private project with, Creating a Private Project from the Welcome Screen-Configuring Your New Repository
- editing files in repository, Editing Files in Your Repository-Editing Files in Your Repository
- exploring your project on, Exploring Your Project-Exploring Your Project
- getting started with, Getting Started-Editing Files in Your Repository
- per-developer forks, Per-Developer Forks
- private team work on, Private Team Work on Bitbucket-Summary
- project documentation in wiki pages, Project Documentation in Wiki Pages-Project Documentation in Wiki Pages
- project governance for nonpublic projects on, Project Governance for Nonpublic Projects
- project setup with, Project Setup-Tracking Your Changes with Issues
- protected branches, Limiting Access with Protected Branches
- pull requests, Pull Requests-Accepting a Pull Request
- shared access, Shared Access
- tracking changes with issues, Tracking Your Changes with Issues-Tracking Your Changes with Issues
- bitHound, Software for Code Reviews, Extending Bitbucket with Atlassian Connect
- blame command, Investigating File Ancestry with blame-Investigating File Ancestry with blame
- branch command, Teamwork in Terms of Git
- branch deployment
- branch types, Sprint-Based Workflow
- branch, create (see checkout command)
- branch-per-feature deployment, Branch-Per-Feature Deployment-Branch-Per-Feature Deployment
- branches
- butter tart recipe example, Teamwork in Terms of Git, Butter Tarts-van der Heyden Butter Tarts
- creating new, Creating New Branches-Creating New Branches
- defined, Branching Strategies
- for experimental work, Using Branches for Experimental Work
- for teams of one, Working with Branches-Creating New Branches
- keeping up to date, Keeping Branches Up to Date-Keeping Branches Up to Date
- listing, Listing Branches
- unmerging, Unmerging a Branch-Unmerging a Branch, Unmerging a Shared Branch-Unmerging a Shared Branch
- updating list of remote branches, Updating the List of Remote Branches
- using different, Using a Different Branch
- working with, Working with Branches-Creating New Branches
- branching strategies, Branching Strategies-Summary
- Brew, Resolving Merge and Rebase Conflicts
- broken branches, Comparative Studies of Historical Records
- Brown, Sunni, Meeting as a Team
- browser-based text editor
- bugs, finding and fixing (see debugging)
- Buildkite, Administrative Dashboard
- butter tart recipes (forking/branching example), Teamwork in Terms of Git, Butter Tarts-van der Heyden Butter Tarts
C
- cached parameter, Combining Commits with Reset
- Canonical, Copyright and Contributor Agreements
- cd shell command, Command Reference
- cd [directory name] shell command, Command Reference
- Chacon, Scott, Branch-Per-Feature Deployment
- changes, proposed
- checkout command, Command Reference
- Chef, The People on Your Team, Copyright and Contributor Agreements
- Chernoff, Chris, OS X Gotchas
- cherry-pick command, An Overview of Locating Lost Work
- clone command, Consumers, Maintainers
- clones, zipped packages vs., Consumers
- cloning (see git clone [URL] command)
- cloning repositories, Teamwork in Terms of Git
- co-maintainership, Granting Co-Maintainership-Granting Co-Maintainership
- Code of Conduct (CoC) document, Code of Conduct
- code reviews, software for, Software for Code Reviews
- Coder, Software for Code Reviews
- codes of conduct, Code of Conduct
- coding teams, The People on Your Team
- collaboration, The People on Your Team
- collocated contributor repositories access model, Access Models, Collocated Contributor Repositories Model-Collocated Contributor Repositories Model
- color, adding to Git, Adding Color
- command and control, Command and Control-Summary
- command prompt customization, Customize Your Command Prompt
- commands (see individual command names)
- commit command, Command Reference
- commit messages
- commit process, Teamwork in Terms of Git
- commitment meetings, Tracking Progress
- commits
- company-wide stand-up meetings, Tracking Progress
- configuration, Git, Configuring Git-Line Endings
- consensus shepherds, Types of Reviewers
- consensus-driven development, The People on Your Team
- consensus-driven, leader-approved governance model, Leadership Models
- consumers
- continuous delivery, Mainline Branch Development
- Continuous Delivery (Humble and Farley), Mainline Branch Development
- continuous deployment, Mainline Branch Development
- continuous integration, Mainline Branch Development
- contractors
- contributors
- conventions, branching strategy, Choosing a Convention
- copyright agreements, Copyright and Contributor Agreements
- creating clones, Teamwork in Terms of Git
- Creative Commons license, Copyright and Contributor Agreements, Distribution Licenses
- creative thinking, Thinking Strategies
- custom access models, Custom Access Models
- CVS, Access Models
D
- debugging, Finding and Fixing Bugs-Summary
- decision thinking, Thinking Strategies
- default branches, Mainline Branch Development
- deleted file, mid-rebase conflict from, Mid-Rebase Conflict from a Deleted File-Mid-Rebase Conflict from a Deleted File
- deployment, Mainline Branch Development
- design critique, Types of Reviews
- detached HEAD state, Updating Branches
- developers
- as consumers, Consumers-Consumers
- as contributors, Contributors
- as maintainers, Maintainers-Maintainers
- setup for multi-person teams, Setting Up the Developers-Maintainers
- trusted, with no peer review, Trusted Developers with No Peer Review-Trusted Developers with No Peer Review
- trusted, with peer review, Trusted Developers with Peer Review
- untrusted, with independent quality assurance, Untrusted Developers with Independent Quality Assurance
- untrusted, with QA gatekeepers, Untrusted Developers with QA Gatekeepers
- development
- Dia, Documenting Your Process
- diff command, Reviewing the Proposed Changes
- diff program, Dispersed Contributor Model
- DigitalOcean, Installing GitLab
- dir shell command, Command Reference
- directed acyclic graph (DAG), Mainline Branch Development
- discreet repositories, Project Governance for Nonpublic Projects
- dispersed contributor access model, Dispersed Contributor Model-Dispersed Contributor Model
- distributed version control, Command and Control
- distribution licenses, Distribution Licenses
- Docker, The People on Your Team
- documentation
- Driessen, Vincent, Scheduled Deployment
- Drupal, Leadership Models
- Drupal Code of Conduct, Code of Conduct
- Drupal Project module, Documenting Encoded Decisions
- Dymitruk, Adam, Branch-Per-Feature Deployment
F
- Facebook, Mainline Branch Development
- Farley, David, Mainline Branch Development
- Fedora, upgrading Git on, Upgrading on *nix Systems
- feedback (review process), Preparing Your Feedback
- fetch command, Teamwork in Terms of Git, Collaborating on Nonsoftware Projects, Uploading the Project Repository, Consumers, Reviewing Work, Trusted Developers with No Peer Review
- files, restoring, Restoring Files
- filter-branch command, Really Removing History, Command Reference
- Flickr, Code of Conduct, Mainline Branch Development
- forks/forking, Teamwork in Terms of Git
- Free Libre Open Source Software (FLOSS), Copyright and Contributor Agreements
- freelancers, copyright and, Copyright and Contributor Agreements
G
- Gamestorming (Gray, Brown, Macanufo), Meeting as a Team
- gc command
- Gerrit, Software for Code Reviews
- Git
- adding color to, Adding Color
- command prompt customization, Customize Your Command Prompt
- commit message editor changes, Changing the Commit Message Editor
- configuring, Configuring Git-Line Endings
- configuring to ignore system files, Ignoring System Files
- converting an existing project to, Converting an Existing Project to Git-Converting an Existing Project to Git
- finding command line for, Finding the Command Line
- GitHub terminology vs., Collocated Contributor Repositories Model
- installers for, Installing Git and Upgrading
- installing latest version of, Installing the Latest Version of Git-OS X Gotchas
- line ending configuration, Line Endings
- OS X installation issues, OS X Gotchas
- teamwork in terms of, Teamwork in Terms of Git-Summary
- upgrading on *nix systems, Upgrading on *nix Systems
- user name/email configuration, Identifying Yourself
- git command (see individual command names)
- git commands, summary, Command Reference, Command Reference
- Git for Knitters, Teamwork in Terms of Git
- Git for Teams, Working Locally
- Git Fundamentals for Web Developers (Mitchell), Publishing Work
- Git hosting
- git-imerge, Resolving Merge and Rebase Conflicts
- GitFlow
- GitHub
- account creation on, Creating an Account-SSH Keys
- contributing to projects, Contributing to Projects-Initiating a Pull Request
- downloading repository snapshots, Downloading Repository Snapshots
- forking, Forking a Project
- getting started on, Getting Started on GitHub-Updating Your Local Repository
- Git terminology vs., Collocated Contributor Repositories Model
- granting co-maintainership, Granting Co-Maintainership-Granting Co-Maintainership
- open source projects on, Open Source Projects on GitHub-Summary
- organization creating on, Creating an Organization
- personal repositories on, Personal Repositories-Updating Your Local Repository
- public projects on, Using Public Projects on GitHub-Working Locally
- pull request initiation, Initiating a Pull Request-Initiating a Pull Request
- pull requests with merge conflicts, Pull Requests with Merge Conflicts
- repository creation for, Creating a Project Repository
- reviewing/accepting pull requests, Reviewing and Accepting Pull Requests
- running your own project, Running Your Own Project-Pull Requests with Merge Conflicts
- SSH keys for, SSH Keys
- tracking changes with issues, Tracking Changes with Issues-Tracking Changes with Issues
- working locally, Working Locally-Working Locally
- GitHub Flow, Branch-Per-Feature Deployment
- gitk command, Reviewing the Proposed Changes
- GitLab, Issue-Based Version Control
- access control, Access Control-Limiting Access with Protected Branches
- adding people to groups, Adding People to Groups-Adding People to Groups
- adding people to projects, Adding People to Projects-Adding People to Projects
- adding projects to groups, Adding Projects to Groups-Adding Projects to Groups
- administrative account configuration, Configuring the Administrative Account
- administrative dashboard, Administrative Dashboard-Administrative Dashboard
- creating a project with, Creating a Project
- creating user accounts, Creating User Accounts-Creating User Accounts
- getting started with, Getting Started-Administrative Dashboard
- groups, Groups-Adding Projects to Groups
- installing, Installing GitLab-Installing GitLab
- limiting access with protected branches, Limiting Access with Protected Branches
- limiting activities with project roles, Limiting Activities with Project Roles
- milestones, Milestones
- project visibility, Project Visibility
- projects, Projects
- self-hosted collaboration with, Self-Hosted Collaboration with GitLab-Summary
- user accounts for, User Accounts-Adding People to Projects
- GitLab Flow, State Branching
- Gitorious, Creating a Project
- Google, Creating a New Project, Creating User Accounts
- Google Calendar, Tracking Progress, Copyright and Contributor Agreements
- Google Code, Creating a Project
- Google Docs, Sprint-Based Workflow
- Google Hangouts, Tracking Progress
- GoToMeeting, Tracking Progress
- governance (see project governance)
- governance models, Leadership Models
- GPL, Distribution Licenses
- Gravatar, Administrative Dashboard
- Gray, Dave, Meeting as a Team
L
- LDAP, Creating User Accounts
- Lead and Succeed in 4 Different Dimensions (program), Thinking Strategies
- leadership models, Leadership Models
- leadership training programs, Thinking Strategies
- licensing, Document the Project in a README
- line endings, Git configuration for, Line Endings
- LinkedIn, Software for Code Reviews
- Linux, Distribution Licenses
- list parameter, Listing Branches
- local repositories
- log command, Command Reference, Command Reference
- ls -a shell command, Command Reference
- Lullabot, Tracking Progress
M
- Macanufo
- mainline branch method, Mainline Branch Development-Mainline Branch Development
- maint (maintenance) integration branch, State Branching
- maintainers
- Managing Chaos (Welchman), Leadership Models
- master integration branch, State Branching
- meetings
- mentoring, The People on Your Team
- merge command, Teamwork in Terms of Git, Summary, Command Reference
- merge conflicts
- merge requests, Collocated Contributor Repositories Model, Collocated Contributor Repositories Model
- merge, rebase vs., Keeping Branches Up to Date
- Microsoft, Project Governance
- mistakes, undoing (see rollbacks)
- MIT License, Distribution Licenses
- Mitchell, Lorna, Publishing Work
- mkdir shell command, Command Reference
O
- OmniAuth, Creating User Accounts
- Omnibus, Installing GitLab
- OmniGraffle, Documenting Your Process
- one-on-one meetings, Tracking Progress
- open source projects, GitHub, Open Source Projects on GitHub-Summary
- account creation on, Creating an Account-SSH Keys
- and personal repositories, Personal Repositories-Updating Your Local Repository
- contributing to projects, Contributing to Projects-Initiating a Pull Request
- downloading repository snapshots, Downloading Repository Snapshots
- forking, Forking a Project
- getting started on, Getting Started on GitHub-Updating Your Local Repository
- granting co-maintainership, Granting Co-Maintainership-Granting Co-Maintainership
- organization creating on, Creating an Organization
- public projects on, Using Public Projects on GitHub-Working Locally
- pull request initiation, Initiating a Pull Request-Initiating a Pull Request
- pull requests with merge conflicts, Pull Requests with Merge Conflicts
- repository creation for, Creating a Project Repository
- reviewing/accepting pull requests, Reviewing and Accepting Pull Requests
- running your own project, Running Your Own Project-Pull Requests with Merge Conflicts
- SSH keys for, SSH Keys
- tracking changes with issues, Tracking Changes with Issues-Tracking Changes with Issues
- working locally, Working Locally-Working Locally
- OpenStack, Software for Code Reviews
- operations teams, The People on Your Team
- organizations (GitHub), Creating an Organization
- origin command, Uploading the Project Repository
- OS X
- overcategorization, avoiding, Ticket Progression
P
- patch files, Dispersed Contributor Model
- patch parameter, Adding Partial File Changes to a Repository
- Payment Card Industry (PCI), Project Governance for Nonpublic Projects
- peer reviews, The People on Your Team
- Pencil, Documenting Your Process
- permissions, establishing, Establishing Permissions
- personal repositories, GitHub, Personal Repositories-Updating Your Local Repository
- Pivotal Tracker, Documenting Encoded Decisions
- private projects (see nonpublic projects)
- private teams (Bitbucket), Private Team Work on Bitbucket-Summary
- product backlog, Ticket Progression
- Product Owner (see team composition)
- progress, tracking, Tracking Progress
- project deep dive meetings, Tracking Progress
- project governance, Project Governance-Code of Conduct
- Project Management Committee
- project setup
- protected branches, Limiting Access with Protected Branches
- pu integration branch, State Branching
- public projects, GitHub, Using Public Projects on GitHub-Working Locally
- contributing to projects, Contributing to Projects-Initiating a Pull Request
- downloading repository snapshots, Downloading Repository Snapshots
- forking, Forking a Project
- granting co-maintainership, Granting Co-Maintainership-Granting Co-Maintainership
- pull request initiation, Initiating a Pull Request-Initiating a Pull Request
- pull requests with merge conflicts, Pull Requests with Merge Conflicts
- repository creation for, Creating a Project Repository
- reviewing/accepting pull requests, Reviewing and Accepting Pull Requests
- running your own project, Running Your Own Project-Pull Requests with Merge Conflicts
- tracking changes with issues, Tracking Changes with Issues-Tracking Changes with Issues
- working locally, Working Locally-Working Locally
- public SSH key, retrieving, Retrieving Your Public SSH Key
- pull command, Teamwork in Terms of Git, Keeping Branches Up to Date
- pull request auto reviewers, Extending Bitbucket with Atlassian Connect
- pull requests
- PullReview, Software for Code Reviews
- Puppet, The People on Your Team, Copyright and Contributor Agreements
- push
- push command, Teamwork in Terms of Git, Summary, Uploading the Project Repository
R
- Rails, Distribution Licenses
- README files, Document the Project in a README
- reasonable restraint, Copyright and Contributor Agreements
- rebase command, Begin Rebasing, Working with Commits, Keeping Branches Up to Date
- rebasing, Updating Branches, Rebasing Step by Step-Mid-Rebase Conflict from a Single File Merge Conflict
- Redmine, Documenting Encoded Decisions, Administrative Dashboard
- reflog command, Command Reference
- release schedules
- remote branches, updating list of, Updating the List of Remote Branches
- remote command
- remote repositories
- repositories, Teamwork in Terms of Git-Teamwork in Terms of Git
- adding changes to, Adding Changes to a Repository-Ignoring Files
- adding partial file changes to, Adding Partial File Changes to a Repository
- branch maintenance, Branch Maintenance
- cloning, Teamwork in Terms of Git
- collocated contributor model, Collocated Contributor Repositories Model-Collocated Contributor Repositories Model
- committing partial changes to, Committing Partial Changes
- connecting to remote, Connecting to Remote Repositories-Branch Maintenance
- creating, Creating a Project Repository
- creating new projects, Creating a New Project
- detailed commit messages, Writing Extended Commit Messages
- downloading snapshots of, Downloading Repository Snapshots
- ignoring files, Ignoring Files
- local, for teams of one, Creating Local Repositories-Reviewing History
- personal, Personal Repositories-Updating Your Local Repository
- pushing changes to, Pushing Your Changes
- removing file from stage, Removing a File from the Stage
- removing history of, Really Removing History-Really Removing History
- second remote connection for, Adding a Second Remote Connection
- reset command, Restoring Files, Combining Commits with Reset-Combining Commits with Reset, Command Reference
- restoring files, Restoring Files
- restraint of trade clause, Copyright and Contributor Agreements
- retrospective meetings, Wrap-Up and Retrospectives
- reverse engineering, Copyright and Contributor Agreements
- revert command, Working with Commits, Reverting a Previous Commit, Command Reference
- Review Board (software), Software for Code Reviews
- review process, Ready for Review-Summary
- rollbacks, Rollbacks, Reverts, Resets, and Rebasing-Summary
- altering commits with interactive rebasing, Altering Commits with Interactive Rebasing-Altering Commits with Interactive Rebasing
- amending commits, Amending Commits
- best practices for, Best Practices-Using Branches for Experimental Work
- combining commits with reset, Combining Commits with Reset-Combining Commits with Reset
- command reference for, Command Reference-Command Reference
- commits and, Working with Commits-Unmerging a Branch
- describing your problem, Describing Your Problem-Describing Your Problem
- locating lost work, An Overview of Locating Lost Work-An Overview of Locating Lost Work
- removing history completely, Really Removing History-Really Removing History
- restoring files, Restoring Files
- undoing shared history, Undoing Shared History-Unmerging a Shared Branch
- unmerging a branch, Unmerging a Branch-Unmerging a Branch
- unmerging a shared branch, Unmerging a Shared Branch-Unmerging a Shared Branch
- using branches for experimental work, Using Branches for Experimental Work
S
- scheduled deployment branching, Scheduled Deployment-Scheduled Deployment
- Schindelin, Johannes, Installing the Latest Version of Git
- Scrum, Ticket Progression
- ScrumMaster (see team composition)
- Sculpin, Teamwork in Terms of Git, Working Locally
- security reviews, The People on Your Team
- self-managing teams, The People on Your Team
- semantic versioning, State Branching
- senior developers, benefits to, Types of Reviewers
- senior reviewers, benefits to, Types of Reviewers
- shared branches, unmerging, Unmerging a Shared Branch-Unmerging a Shared Branch
- shared history, undoing, Undoing Shared History-Unmerging a Shared Branch
- shared maintenance access model, Access Models, Shared Maintenance Model
- shell commands, Command Reference
- show command
- sidekiq, Administrative Dashboard
- single repository, shared access model, Access Models
- Skype, Configuring the Administrative Account
- social coding, Project Governance for Nonpublic Projects
- solo developers (see teams (one member))
- sprint demo meetings, Tracking Progress
- sprint planning meetings, Tracking Progress
- sprint-based workflow, Sprint-Based Workflow-Sprint-Based Workflow
- sprints, Mainline Branch Development
- SSH keys, SSH Keys, SSH Keys-Retrieving Your Public SSH Key
- staged parameter, Combining Commits with Reset
- staging changes, Combining Commits with Reset
- stand-ups (see commitment meetings)
- stash
- state branching, State Branching-State Branching
- status command, Command Reference
- Subversion, Distribution Licenses, Access Models, Limiting Access with Protected Branches
- system files, ignoring, Ignoring System Files
T
- tab completion, Adding Changes to a Repository
- tag command, Summary
- tags
- team composition
- teams (multiple-member), Teams of More than One-Summary
- and empathy, Cultivating Empathy
- creating new project, Creating a New Project
- developer setup for, Setting Up the Developers-Maintainers
- establishing permissions, Establishing Permissions
- for nonsoftware projects, Collaborating on Nonsoftware Projects
- kickoff meetings, Kickoff
- meetings for, Meeting as a Team-Wrap-Up and Retrospectives
- members of, The People on Your Team
- participating in development, Participating in Development-Publishing Work
- progress-tracking meetings, Tracking Progress
- project setup, Setting Up the Project-Document the Project in a README
- sample workflows for, Sample Workflows-Untrusted Developers with Independent Quality Assurance
- teamwork in terms of Git, Teamwork in Terms of Git-Summary
- thinking strategies for, Thinking Strategies-Thinking Strategies
- trusted developers with no peer review, Trusted Developers with No Peer Review-Trusted Developers with No Peer Review
- uploading project repository, Uploading the Project Repository-Uploading the Project Repository
- working in, Working in Teams-Summary
- wrap-up/retrospective meetings, Wrap-Up and Retrospectives
- teams (one-member), Teams of One-Summary
- technical architecture review, Types of Reviews
- technical review board governance model, Leadership Models
- testing process, The People on Your Team
- testing teams, The People on Your Team
- text editor, browser-based
- thinking strategies, Thinking Strategies-Thinking Strategies
- ticket progression, Documenting Encoded Decisions
- ticket-based peer code review, Types of Reviews
- ticketing systems, Documenting Encoded Decisions
- touch shell command, Command Reference
- track command, Teamwork in Terms of Git
- tracking progress, meetings for, Tracking Progress
- true merges, Branch Maintenance
- trusted developers
- Twitter, Creating a New Project, Configuring the Administrative Account, Administrative Dashboard
- Typo3, Software for Code Reviews
U
- Ubuntu
- Ubuntu Code of Conduct, Code of Conduct
- understanding thinking, Thinking Strategies
- undo methods, Describing Your Problem
- undoing (see rollbacks)
- Unfuddle, Documenting Encoded Decisions
- Unix
- unmerging a branch, Unmerging a Branch-Unmerging a Branch
- untracked changes, Combining Commits with Reset
- untrusted developers
- updating branches, Updating Branches-Updating Branches
- upstream branch, Working Locally
- upstream project, Collocated Contributor Repositories Model
- urgent (term), Scheduled Deployment
- user acceptance testing, Types of Reviews
W
- web editor
- Welchman, Lisa, Leadership Models
- Wiele, Bob, Thinking Strategies
- wiki pages, Bitbucket, Project Documentation in Wiki Pages-Project Documentation in Wiki Pages
- Windows
- WordPress, Distribution Licenses, Collocated Contributor Repositories Model
- work for hire copyright arrangements, Copyright and Contributor Agreements
- work, reviewing, Reviewing Work-Merging Completed Work
- workflow
- and teamwork in terms of Git, Teamwork in Terms of Git-Summary
- basic example, A Basic Workflow-Untrusted Developers with QA Gatekeepers
- branching strategies, Branching Strategies-Summary
- command and control, Command and Control-Summary
- debugging, Finding and Fixing Bugs-Summary
- effective styles, Workflows That Work-Summary
- encoded decision documentation, Documenting Encoded Decisions
- evolving, Evolving Workflows-Documenting Encoded Decisions
- for ongoing development, Ongoing Development
- for releasing software according to schedule, Releasing Software According to Schedule-Post-Launch Hotfix
- for teams of more than one, Working in Teams-Summary, Teams of More than One-Summary
- for teams of one, Teams of One-Summary
- nonsoftware projects, Collaborating on Nonsoftware Projects
- ongoing development, Ongoing Development
- post-launch hotfix, Post-Launch Hotfix
- process documentation, Documenting Your Process
- review process, Ready for Review-Summary
- rollbacks, Rollbacks, Reverts, Resets, and Rebasing-Summary
- sprint-based, Sprint-Based Workflow-Sprint-Based Workflow
- stable release publication, Publishing a Stable Release
- ticket progression, Documenting Encoded Decisions
- trusted developers with peer review, Trusted Developers with Peer Review
- untrusted developers with QA gatekeepers, Untrusted Developers with QA Gatekeepers
- working branches, Comparative Studies of Historical Records
- wrap-up meetings, Wrap-Up and Retrospectives
- write access, Collocated Contributor Repositories Model
Git for Teams
Published by
O'Reilly Media, Inc., 2015