The following pages are tagged with
| Title | Excerpt |
|---|---|
| Approve or Reject an Unmanaged SCM Server Access Request | When a user asks for access to an unmanaged SCM server, an administrator must approve or reject the request. |
| Approve or Reject a Source Control Repository Request | When a user requests a source code repository on a source control server for which you have required approval, a TeamForge administrator must approve the req... |
| Approve or Reject Repository Delete Requests | SCM system maintenance requests (such as a repository delete request) must be approved (or rejected) by an administrator. |
| Associate Code Commits | Create associations between code commits and other Digital.ai TeamForge items, such as tracker artifacts or documents, to help define relationships, track de... |
| Change the scmviewer Password | It is recommended to change the scmviewer password after installing TeamForge. |
| Check Command History | Recent command history for a replica server or a specific repository allows you to check for errors and see whether there are pending commands. |
| Check Out Code | You can use the checkout command to check out the code from Subversion or GIT repository. |
| Control Your Code Review Policy | You can control all Gerrit Code Review features directly from TeamForge by specifying a code review policy. |
| TeamForge Maven Deploy Plugin | The Digital.ai TeamForge Maven Deploy Plugin can be configured to post binary artifact deployment information to TeamForge via the Webhooks-based Event Broke... |
| Connect to a Subversion Edge Console | When a Subversion Edge server has been converted to a SCM Integration server in TeamForge, you can log into its management console from within TeamForge. |
| Create a Source Code Repository | Each project can have one or more source code repositories. Before you can create a source code repository, a site administrator must first add one or more S... |
| Delete a Source Code Repository | When you delete a repository, a request is submitted to the administrator for approval. |
| Edit SCM Integration Details | You can move or reconfigure a source control server without having to reintegrate the server into TeamForge. |
| Get the Code | Browse TeamForge to find the code you want to work on, then check out the code. |
| TeamForge-Git Integration | TeamForge supports integration with Git, a distributed version control tool powered by Gerrit. |
| Import External Git Repositories into TeamForge from the Code Browser UI | External public Git repositories can now be imported into TeamForge from the Code Browser UI. |
| Integrate a Source Code Server | A site must have one or more servers to handle source code repositories and users. The source code server can be the same server as the application server or... |
| Work with the Internal Code Browser | For Subversion and Git repositories, you have the option to use the TeamForge code browser which is turned on by default while integrating the source code se... |
| Linkify Custom Object IDs in Code Browser | Include custom object IDs in your commit messages and have them automatically converted to hyperlinks. This is possible if you set up custom object ID mappin... |
| Manage Binary Repositories | With TeamForge—Nexus integration enabled, you can create one or more binary repositories and link them to your project. |
| Manage Replicas | A replica server in TeamForge is a Subversion Edge server that replicates the content of an existing core SCM integration server. |
| Mass Configuration of Repository Policies Within a Project | You may often want to apply a specific set of policies to more than one repository. You can just select multiple repositories within a project and apply your... |
| Move a Source Code Repository | When the existing code base for an application may need to be managed by a different team or project, you can move the source code repository from the first ... |
| Review Code (Gerrit Single-commit and Pull Request Reviews) | TeamForge provides a unified code review experience as it supports both Pull Request and Gerrit single-commit reviews. |
| Quality Gates and Review Rules | This topic discusses quality gates and review rules from an administrator perspective. It also discusses some of the known issues with the project level `rul... |
| Replicate a Subversion Repository | When a Subversion Edge replica has been successfully registered with a TeamForge SCM integration server, it is available to project administrators in project... |
| Search Code | Integration with Black Duck Code Sight (BDCS) is no longer supported in TeamForge 17.1 and later. TeamForge 17.1 (and later) is equipped with its own code se... |
| Set up Git Replica Servers | On sites distributed across multiple geographic locations, Git Replica Servers are local and remote mirror servers that can provide up-to-date copies of the ... |
| Set up LFS | Git Large File Storage (LFS) is a Git extension for versioning large files. Git LFS replaces large files such as audio samples, videos, datasets, and graphic... |
| FAQs on Source Code (SCM) | These are some of the frequently asked questions on SCM related activities in TeamForge. |
| Source Code (SCM) | These are some of the frequently asked questions on SCM related activities in TeamForge. |
| Synchronize TeamForge Source Control Integrations | Any time you upgrade your TeamForge site or a source control application, you must ensure that your users can still access their source code. |
| UserFilter Removal | The `UserFilter` removal from the Quality Gates is a direct outcome of the removal of the `current_user` predicate from the open source Gerrit. |
| View Code Commits | To stay up to date with code development on a project, browse the code commits made to each repository integrated into your TeamForge site. |