gitli | Simple git extension to manage issues

If I found the correct documentation page, blobContents looks like a non-monadic function, so you can't use bc <- blobContents blob. Use instead let bc = blobContents blob.

This is consistent with the error message, which states that the actual type is not wrapped under IO.

init is a member function of GitList and therefore needs to be called on an instance of GitList. The same is true of a number of other function calls in main.

So, your code should look like this:

It seems that your Jest setup couldn't read the Vuejs as a ES6 file. You could try by editing your jest.config.js file and adding:

Try first to initiate your local Git repo with:

So after some extensive poking around the DB, I have managed to hack together a solution. I couldn't find a way to do it through the UI, but there are two key things that have to be done in the DB to make it work.

First, you need to enable the feature, which is enabled in the repository settings. While I couldn't find a setting in the UI, if you adjust anything from the default settings on the repo, a JSON object is saved to the dbo.tbl_PolicyConfigurationRevision table which includes an "optimizedByDefault" element which will be null, change it from null to true and the feature will now be enabled on the repo in question.

Alternately, this can be accomplished using the Policy Configuration endpoint for the TFS Rest API as described here. It's a bit more involved and still involves tweaking the JSON, but it goes through officially exposed channels without requiring direct DB manipulation and will properly version the configuration change.

Second, you need to specify what the "important" refs are. There is a stored proc and a custom data type to help with this. dbo.prc_UpdateGitLimitedRefCriteria takes the partitionId, dataspaceId, repositoryId and two custom table data type records for the exactRefs matches and the namespaceRefs matches. Build up the tables with your important refs in them and call the stored proc to add them to the list.

It appears that this ends up going through the prc_QueryGitRefs stored proc for filtering the refs, so you can look in there if you need more detail about how to format them so that processing works correctly.

After a bit more experimentation, it appears that there is an undocumented API endpoint for limitedRefCriteria as well that supports getting and updating ref criteria.

This is a hideous hack, and provides only a partial solution.

I ended up just using the "old submodules" option:

1. Move subrepo folders to the desktop HDD, somewhere near the superrepo's git dir; write down their original paths
2. Make sure that the superrepo workdir is clean
3. Add subrepos back to the superrepo using git submodule add --name NAME RESERVE_HDD_PATH PORTABLE_HDD_PATH, where NAME is some valid dir name, RESERVE_HDD_PATH is the path to subrepo on the desktop HDD, PORTABLE_HDD_PATH is the original subrepo path that you wrote down in step 1, relative to the superrepo's root
4. Delete the .git files that were created in workdir, and copy the original subrepos back from the desktop HDD instead of those files
5. Remove the modules folder from the superrepo's git dir (it's superfluous)
6. Add subrepos which are now on the portable HDD as remotes to the corresponding subrepos which are on the desktop HDD.

That's it. Now you can work in subrepos using the portable HDD, and every time you connect it to the desktop and make a commit of the superrepo, it will remember the current commits of all subrepos. You just have to make a reserve copy of those subrepos, e.g. with a script like this (residing on the desktop HDD near the subrepo folders):

Using the fact that a Git repo is self-contained and can just be copied, we only need some way to make a copy and convert from bare to non-bare for our first few attempts.

Cloning is still the best form of initial copying, if that option is possible (see work-arounds 1 and 2). If not, we can just straight copy from the server, if access is available, and convert it manually (see #3). Failing that, perhaps copying/cloning a smaller piece of the repo will work?

Get on the server (if you have access), clone to a usb drive folder (as a non-bare repo), stick USB into target machine, and just move/copy it to the final location you want the repo. Git command should be:

Only adding services.AddAutoMapper(); to the ConfigureServices method would not work for you. You have to configure AutoMapper as follows: