Downloads:

21,793

Downloads of v 2.0.3.20131127:

397

Last Update:

14 Dec 2013

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

GIT TFS Codeplex

Git-TF

This is not the latest version of Git-TF available.

2.0.3.20131127 | Updated: 14 Dec 2013

Downloads:

21,793

Downloads of v 2.0.3.20131127:

397

Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

GIT TFS Codeplex

Git-TF 2.0.3.20131127

This is not the latest version of Git-TF available.

All Checks are Unknown

2 Test of Unknown Status


Validation Testing Unknown


Verification Testing Unknown

To install Git-TF, run the following command from the command line or from PowerShell:

>

To upgrade Git-TF, run the following command from the command line or from PowerShell:

>

To uninstall Git-TF, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade git-tf -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade git-tf -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure git-tf installed
  win_chocolatey:
    name: git-tf
    state: present
    version: 2.0.3.20131127
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'git-tf' do
  action    :install
  version  '2.0.3.20131127'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: git-tf,
    Version: 2.0.3.20131127,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller git-tf
{
   Name     = 'git-tf'
   Ensure   = 'Present'
   Version  = '2.0.3.20131127'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'git-tf':
  provider => 'chocolatey',
  ensure   => '2.0.3.20131127',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install git-tf version="2.0.3.20131127" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

Git-TF is a set of cross-platform, command line tools that facilitate sharing of changes between TFS and Git. These tools allow a developer to use a local Git repository, and configure it to share changes with a TFS server. Using the tools, changes made in TFS can be pulled into a local Git repository, and changes made in the Git repository can be checked in to TFS. These tools can be used by individuals or teams collaborating using Git.


In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Git-TF 2.0.3.20131127 397 Saturday, December 14, 2013 Unknown
Git-TF 2.0.2.20130214 1672 Friday, February 15, 2013 Unknown
Git-TF 2.0.1.20130108 645 Wednesday, January 9, 2013 Unknown
Git-TF 2.0.1.20130107 411 Tuesday, January 8, 2013 Unknown
Git-TF 2.0.0.20121030 674 Thursday, November 1, 2012 Unknown
Git-TF 1.0.1.20120827 444 Tuesday, August 28, 2012 Unknown
Git-TF 1.0.1 411 Tuesday, August 28, 2012 Unknown
Git-TF 1.0 420 Wednesday, August 22, 2012 Unknown
Discussion for the Git-TF Package

Ground Rules:

  • This discussion is only about Git-TF and the Git-TF package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Git-TF, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus