DEV Community: Simon Osipov

Multiple GitHub accounts on one laptop

Simon Osipov — Tue, 18 Jan 2022 18:49:51 +0000

Imagine the next situation:

You have only one laptop
You have your personal GitHub account
Your employer stores code on GitHub as well
You need to commit your personal code to your personal repositories but also work code to the employer`s repositories.
You can`t do this from your personal account but do not want to create an additional one (with corporate email)

What to do in this situation? There is a way, how you can configure your laptop to commit to work repositories with work credentials, and to personal one with your personal one.

This solution is based on 2 aspects:

correcting SSH config
git URL re-writing

The main advantage of this approach is that it doesn't require any additional work to get it right. You will not need to change remote URLs or remember to clone things differently. The second part ( the URL rewriting) will take care of it.

First of all, let's correct our .ssh config. Assuming you have 2 ssh keys, your personal (github_personal) and your work (github_work). How to create ssh keys you can read in the GitHub docs.

~/.ssh/config

Host github.com
  HostName github.com
  User git
  IdentityFile ~/.ssh/github_personal

# Work GitHub
Host github-work
  HostName github.com
  User git
  IdentityFile ~/.ssh/github_work

Host *
  AddKeysToAgent yes

Both this configs have same user and domain, but we will take care about it later. Next - global git config.

~/.gitconfig

Here we need to add our default name and email (the one we used in ssh creation for our personal account)

[user]
    name = My Name
    email = personal@personal.email

[includeIf "gitdir:~/path/work_dir/"]
    path = ~/path/work_dir/.gitconfig

[url "github-work:work-github-org-name/"]
    insteadOf = git@github.com:work-github-org-name/

What happens here? First, set our default name and email. Second, we point to use local .gitconfig file for all repositories located by mask ~/path/work_dir/. And the last, replace github.com (default account for Github) with the profile we set under github-work in .ssh/config.

The last part is modification of local .gitconfig for all our working repositories:

~/path/work_dir/.gitconfig
It is easy - just replace your email with your corporate one.

[user]
    email = work@work.email

That is all! As long as you keep all your work repos under ~/path/work_dir/ and personal stuff elsewhere, git will use the correct SSH key when doing pulls/clones/pushes to the server, and it will also attach the correct email address to all of your commits.

How to check? Clone repository via SSH, cd to that folder and execute git config --get user.email

How to forbid the creation/linking of subtask for a card in YouTrack

Simon Osipov — Mon, 13 Apr 2020 08:25:27 +0000

Problem: I would like to forbid the situation when someone creates a card with type “User Story” and marks it as “subtask of” another card.

In our case, User Story is a top hierarchy card, so it can't be a subtask of any other card. But sometimes people forget that and link two cards with that type of link instead of “relates to” or “depends on”. So, how would you forbid creation or linking as subtask certain card type in Youtrack? Here is the code snippet:

var entities = require('@jetbrains/youtrack-scripting-api/entities');
var workflow = require('@jetbrains/youtrack-scripting-api/workflow');
exports.rule = entities.Issue.onChange({
  title: workflow.i18n('Task default description'),
  guard: function(ctx) {
    var issue = ctx.issue;
    return issue.links["subtask of"].added.isNotEmpty() | issue.links["subtask of"].isNotEmpty();

  },
  action: function(ctx) {
    var issue = ctx.issue;
    var issue_type = issue.fields["Card Type"].name;
    if (issue_type === "US" | issue.becomes("Card Type", "US")) {  
      workflow.check(!issue.links["subtask of"].added.isNotEmpty() & !issue.links["subtask of"].isNotEmpty(),
"User Story can`t be subtask of any other card, only as standalone card.");
    }
  },
  requirements: {}
});

I hope that helps!
Simon Osipov
Web
Twitter
FB
GitHub
LinkedIn
Telegram
Data Engineering TG channel RUS

How to inherit tags in YouTrack from task to subtask

Simon Osipov — Sun, 29 Dec 2019 12:37:43 +0000

If you are using JetBrains YouTrack as your Task tracker, you are probably already familiar with Workflows. This is an event-based code snippet that allows you to perform some routine tasks automatically or on schedule. These workflows are written in JavaScript, so most of the team could easily create routines they need. Because in my team both frontend-developers were very busy with the refactoring of some core module, I decided to write a script on my own.

So, imagine, you have tags in your project and every time you add or remove a tag from a card, you would like to populate this change top-to-bottom and bottoms-up: from task to subtask and from subtask to parent. So, how would you inherit a tag in Youtrack? Here is a code snippet:

var entities = require('@jetbrains/youtrack-scripting-api/entities');
exports.rule = entities.Issue.onChange({
  title: 'Inherit tags',
  guard: function(ctx) {
    return ctx.issue.tags.added.isNotEmpty() || ctx.issue.tags.removed.isNotEmpty();
  },
  action: function(ctx) {
    var issue = ctx.issue;
    issue.links['parent for'].forEach(function(childIssue) {
      issue.tags.added.forEach(function(tag) {
        childIssue.addTag(tag.name);
      });
      issue.tags.removed.forEach(function(tag) {
        childIssue.removeTag(tag.name);
      });
    });
  },
  requirements: {

  }
});

If you would like to copy tag from subtask to parent, here it is:

var entities = require('@jetbrains/youtrack-scripting-api/entities');
exports.rule = entities.Issue.onChange({
  title: 'Populate tags up',
  guard: function(ctx) {
    return ctx.issue.tags.added.isNotEmpty() || ctx.issue.tags.removed.isNotEmpty();
  },
  action: function(ctx) {
    var issue = ctx.issue;
    issue.links["subtask of"].forEach(function(parentIssue) {
      issue.tags.added.forEach(function(tag) {
        parentIssue.addTag(tag.name);
      });
      issue.tags.removed.forEach(function(tag) {
        parentIssue.removeTag(tag.name);
      });
    });
  },
  requirements: {

  }
});

I hope it helps!
Simon Osipov
Web
Twitter
FB
GitHub
LinkedIn
Telegram
Data Engineering TG channel RUS