Skip to content
BranchesTags

Repository files navigation

Deploy request email generator

This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails. The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.

A sample generated email may look like this:

Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage

Clone the repository and then configure the script.

Once the configuration is in place:

  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.

The script should open your preferred email client with the deploy request email.

Referenced issues

Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:

commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests

A deploy request can be marked as a [SPECIAL] one or a [no special] one. This has to do with our deployment practices. If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.

When running the application a prompt gets shown which asks whether the deploy request is special or not. If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.

Configuration

The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository. Copy and tweak the existing settings.yml.sample to your liking.

Here's a brief explanation of what the different settings do:

  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?

About

Generates a feature branch deploy request which is to be sent to the company's deploy officer.

Resources

Readme
License
Activity
Custom properties

Stars

0 stars

Watchers

8 watching

Forks

1 fork
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
GitHub - evokegaming/deploy-request-generator: Generates a feature branch deploy request which is to be sent to the company's deploy officer. · GitHub
Skip to content
BranchesTags
Repository files navigation
Deploy request email generator
This is refinement of a simple Bash-script that my co-worker had written for the purpose of generating deploy request emails.
The tool generates a mailto-link which is then opened with either xdg-open or open, depending on whether you're on Linux or OSX.
A sample generated email may look like this:
Subject: Deploy request [no special] for mm-some_feature_branch

# Branch
mm-some_feature_branch
# Commits
e0b217d Mandatory whitespace commit
8300ada Remove old stuff
db52672 Implement another thing
7a14d55 Fix some thing
# Shortstat
3 files changed, 70 insertions(+), 43 deletions(-)
# Referenced issues
https://issue.tracker.com/issues/57
https://issue.tracker.com/issues/123
https://issue.tracker.com/issues/958

Usage
Clone the repository and then configure the script.
Once the configuration is in place:
  1. Change your directory to the project you wish to send a deploy request from.
  2. Change your git branch to the feature branch you wish to send a deploy request mail for.
  3. Run deployrequest, wherever you've placed it.
The script should open your preferred email client with the deploy request email.
Referenced issues
Do note that the "Referenced issues" feature works on the assumption that you specify what issue a commit references by having dedicated ref-lines (for instance at the end of commits) as follows:
commit 21b6fa0c21fc4d014532265b36ed2e57374f4d8e
Author: Mikael Muszynski <linduxed@gmail.com>
Date: Wed Oct 20 13:49:45 2014 +0200
First line of commit message
Some extra information.
refs #7418

Special deploy requests
A deploy request can be marked as a [SPECIAL] one or a [no special] one.
This has to do with our deployment practices.
If we would need to do something special with our server setup for a build to work, then this needs to be indicated and instructions need to be included.
When running the application a prompt gets shown which asks whether the deploy request is special or not.
If it is, the subject of the mail will be changed and the body will include an extra space where one can include instructions for the deploy officer.
Configuration
The generator needs to be configured with a settings.yml file, which has to be placed at the root of the repository.
Copy and tweak the existing settings.yml.sample to your liking.
Here's a brief explanation of what the different settings do:
  • email_to - What address will the deploy request be sent to.
  • issue_tracker_url - The URL of the issue tracker.
  • default_allowed - Whether the user should be allowed to just press Enter when Y/N choices are presented.
  • default_special - If default_allowed is set to true: is this a special deploy request or not?
  • default_target_branch_is_master - If default_allowed is set to true: is the target branch to merge into master?
About
Generates a feature branch deploy request which is to be sent to the company's deploy officer.
Resources
Readme
License
Activity
Custom properties
Stars
0 stars
Watchers
8 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages