##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
vcs: Minimal change to expose the shadow repository...
vcs: Minimal change to expose the shadow repository Based on my original research, this was the "minimal" starting point. It shows that three concepts are needed for the "repo_name": * From the security standpoint we think of the shadow repository having the same ACL as the target repository of the pull request. This is because the pull request itself is considered to be a part of the target repository. Out of this thought, the variable "acl_repo_name" is used whenever we want to check permissions or when we need the database configuration of the repository. An alternative name would have been "db_repo_name", but the usage for ACL checking is the most important one. * From the web interaction perspective, we need the URL which was originally used to get to the repository. This is because based on this base URL commands can be identified. Especially for Git this is important, so that the commands are correctly recognized. Since the URL is in the focus, this is called "url_repo_name". * Finally we have to deal with the repository on the file system. This is what the VCS layer deal with normally, so this name is called "vcs_repo_name". The original repository interaction is a special case where all three names are the same. When interacting with a pull request, these three names are typically all different. This change is minimal in a sense that it just makes the interaction with a shadow repository barely work, without checking any special constraints yet. This was the starting point for further work on this topic.
ergo - - Load All Authors

File last commit:

r799:98bb3f4f default
r887:175782be default
Show More
rhodecode-toast.less
29 lines | 571 B | text/x-less | LessCssLexer
/ rhodecode / public / js / src / components / rhodecode-toast / rhodecode-toast.less
History | Source | Raw |Copy content |Copy permalink
ergo
notifications: make styling match the design
 r704 @import '../../../../css/variables';
lisaq
css: using variables and mixins for toast component
 r766 @import '../../../../css/mixins';
ergo
notifications: make styling match the design
 r704
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 paper-toast{
width: 100%;
min-width: 400px;
ergo
notifications: restyle a bit so we don't have invisible element obscure html
 r799 padding: 0px;
ergo
toasts: refedined how notifications looks
 r747 --paper-toast-background-color: transparent;
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 --paper-toast-color: #000000;
lisaq
css: using variables and mixins for toast component
 r766 .box-shadow(none);
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 }
paper-toast a{
font-weight: bold
}
.toast-message-holder {
}
.toast-close {
ergo
notifications: restyle a bit so we don't have invisible element obscure html
 r799 right: -5px;
position: absolute;
bottom: -45px;
ergo
toasts: refedined how notifications looks
 r747 paper-button{
lisaq
css: using variables and mixins for toast component
 r766 .box-shadow(0 2px 5px 0 rgba(0, 0, 0, 0.15));
ergo
components: reorganize build pipeline to have nice separation of html/js/css
 r703 }
}
ergo
toasts: refedined how notifications looks
 r747 paper-toast .alert{
ergo
notifications: restyle a bit so we don't have invisible element obscure html
 r799 margin: @padding 0 0 0;
lisaq
css: using variables and mixins for toast component
 r766 .box-shadow(0 2px 5px 0 rgba(0, 0, 0, 0.15));
ergo
toasts: refedined how notifications looks
 r747 }