Details
-
Suggestion
-
Resolution: Answered
-
None
-
None
Description
Using transcrypt git extension is great to hide some files content for some people.
It works great for local repo which have transcrypt enable.
Encrypted file, is a good way/workaround to replace the folder permissions which are present in Centralized SCM, like SVN/Perforce. It's not exactly the same feature, but it quite similar if you just have two type of access/permissions for files in your depot.
And it's far easier to used than having multiple repos with submodule/subtree.
But when the files are push to Bitbucket server, it's not possible to view the encrypted files, because there is no clean/smudge hook on the server, like there is a local repo.
Viewing this encryptedfile will be great for using diff feature on Bitbucket server, but also (and especially) to comment modified encrypted file inside Pull request.
Here the feature have the plugin could do:
- view the encrypted file content in PullRequest
- view the encrypted file content in diff view
- view the encrypted file content in the standard content view
- have a setting by repo to define the transcrypt password that will be used to decrypt the file, and a permission/rights setting with a list of users/groups that will be able to view the encrypted file on this depot using the given password.