GitHub released this nice feature to create PR templates[1]. Me and my team wanted to leverage that. However,I couldn't get it to work in enterprise git.
Is the new feature not available in GitHub Enterprise yet?
[1]https://github.com/blog/2111-issue-and-pull-request-templates
The pull request template feature is not available in GitHub Enterprise as of March 12, 2016. The latest releases of GitHub Enterprise are 2.5.1, 2.4.5, 2.3.9, 2.2.15, and 2.1.20. Features introduced at GitHub.com may make their way into GitHub Enterprise, but it is not guaranteed. For instance, Jupiter notebook support was added to GitHub.com on May 7, 2015, but has not yet made its way into GitHub Enterprise.
GitHub Enterprise release notes can be found here
Related
i'm trying to setup a new gitHub enterprise repo and looking at using "releases". i wanted to try the auto generate release notes feature but I don't have the button that is shown here...
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
is this a problem with my version of github enterprise server (3.3.6), github enterprise server in general or something else i'm not doing?
Looks like it is available from 3.4 release onwards.
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
We are using TFS 2015 On Premise, not in the cloud and I am trying to give access to Stakeholders so they can access the wiki. However, as a stakeholder I keep getting this error:
TF400409: You do not have licensing rights to access this feature: Code
After researching the error it seems to be related to the fact that Stakeholders do not have access to view Code Wikis as shown here. That link is for Azure DevOps and I am not sure if it applies to my case but I cannot find anything else so my assumption is it does apply. Even links within our TFS site, takes us to Azure DevOps for help and thus my assumption is it applies to us as well.
Here is a screenshot from the aforementioned link:
Question
What is the difference between Code Wikis and Project Wikis? It seems I need Project Wikis but how do I create a Project Wiki?
Thanks in advance!
Code Wiki are not available on TFS server 2015. You need to use version TFS 2018 or above for this.
Project Wiki
Every team project can have a wiki. Use the wiki to share information
with your team to understand and contribute to your project.
Each team project wiki is powered by a Git repository in the back-end.
When you create a team project, a Wiki Git repo is not created by
default. Provision a Git repository to store your wiki Markdown files,
or publish existing Markdown files from a Git repository to a wiki.
In the project page, you could directly choose to create project wiki.
Code Wiki
Content that you already maintain in a Git repository can be published to a wiki. For example, this could be content written to
support a software development kit (SDK), product documentation, or
README file. You can publish multiple wikis within a single team
project.
More details about the difference of them, kindly refer our official doc here:
Provisioned wikis vs. published code as a wiki
As how to use them in Azure DevOps/TFS, you could also take a look at this step by step tutorial -- Collaborating using Azure DevOps Wiki
vsts online introduces wiki feature in its latest additions.
Are there any diagramming tool available as a plugin for creating wiki in the newly introduced wiki tool in vsts online?
Based on the wiki extension overview, it will be available.
Built with extensibility in mind
Want to see diagrams, mind maps and more in your wikis?
With the extensibility model we enable integrations with existing
tools to really make your wiki pages come alive.
On the other hand, you can clone it to local and modify, then push to server.
Add and edit pages in your team project wiki
I see this is an old question but there are updates. Azure DevOps Wiki (Services & Server) now supports limited Mermaid diagrams; just Sequence diagrams, Gantt charts, and Flowcharts.
Sadly Azure DevOps Wiki is stuck at an older Mermaid version, making it troublesome to use as the newer, documented Mermaid syntax often does not work.
We're assessing whether to buy either the Standard or Professional version of Araxis merge. The Standard version has no auto merge, but this won't matter if TFS does that for us. But does it??
TFS does support auto-merge and, unfortunately, there's no extensibility point that would let you plug-in Araxis' auto-merge functionality (which, to be honest, is probably better than the auto-merge we shipped in TFS 2010). We do have improvements to our auto-merge coming in TFS 11.
I'm looking for a way to integrate Eclipse/Mylyn with github's project-issues.
I'm aware of the Mylyn-github-connector and the smilebase project, but - unless I'm totally wrong - both connectors only allow to associate existing tasks with github commits. There is no option to use github issues as a task repository.
I also found this slightly related question / answer, but besides the fact that the provided link is dead it seems to focus on the connector itself (not the task repository)
Thanks for answering,
Jan
This is the connector you want: org.eclipse.mylyn.github (it is a fork of the one posted in the related question). I have been using it and it works great.
The GitHub Mylyn Connector is now an official Eclipse project under EGit.
The 1.0 release was part of Indigo and is available from the EGit update site under the Collaboration category:
http://download.eclipse.org/egit/updates
1.1 nightlies are also available with support for pull requests:
http://download.eclipse.org/egit/github/updates-nightly