-
Notifications
You must be signed in to change notification settings - Fork 563
VC (VERSION CONTROL)
The following links provide information on Trilinos version control processes and workflows.
- See How to Do Version Control with Git in Your CSE Project, an IDEAS Productivity "How To" Document.
- Do an initial setup to use git on any new machine.
- Use the simple centralized workflow to integrate and push changes to a shared remote tracking branch (i.e. the 'develop' branch)
- For typical development, most developers will checkout, make changes, and push Trilinos changes to the 'develop' branch.
- To fix defects on a release branch, use the release branch merge workflow.
- Use the tools gitdist and checkin-test.py to help work with Trilinos and extra repositories (e.g. inserted packages like Sundance, CTrilinos, ForTrilinos, Mesquite and MOOCHO as well as extra packages in repos like preCopyrightTrilinos).
Copyright © Trilinos a Series of LF Projects, LLC
For web site terms of use, trademark policy and other project policies please see https://lfprojects.org.
Trilinos Developer Home
Trilinos Package Owners
Policies
New Developers
Trilinos PR/CR
Productivity++
Support Policy
Test Dashboard Policy
Testing Policy
Managing Issues
New Issue Quick Ref
Handling Stale Issues and Pull Requests
Release Notes
Software Quality Plan
Proposing a New Package
Guidance on Copyrights and Licenses
Tools
CMake
Doxygen
git
GitHub Notifications
Mail lists
Clang-format
Version Control
Initial git setup
'feature'/'develop'/'master' (cheatsheet)
Simple centralized workflow
Building
SEMS Dev Env
Mac OS X
ATDM Platforms
Containers
Development Tips
Automated Workflows
Testing
Test Harness
Pull Request Testing
Submitting a Pull Request
Pull Request Workflow
Reproducing PR Errors
Addressing Test Failures
Trilinos Status Table Archive
Pre-push (Checkin) Testing
Remote pull/test/push
PR Creation & Approval Guidelines for Tpetra, Ifpack2, and MueLu Developers