| package dev.anandsharma.corejava.ch3; | |
| import java.io.IOException; | |
| import java.io.PrintWriter; | |
| import java.nio.charset.StandardCharsets; | |
| import java.nio.file.Path; | |
| import java.util.Scanner; | |
| public class FileIOTest1 { | |
| public static final String RW_FILE_PATH = "/Users/anasharm/Downloads/test1.txt"; |
| " .vimrc | |
| " Maintained by: Anand Sharma | |
| " anand.sharma@gmail.com | |
| " Heavily borrowed from https://github.com/zanshin/dotfiles | |
| " Need more studying: https://bitbucket.org/sjl/dotfiles/src/4e6f3d36c2417fd778f30192b90c51795bdcd368/vim/vimrc?at=default | |
| " | |
| " ------------------------------------------------------------------- | |
| " Forget compatibility with vi | |
| " ------------------------------------------------------------------- | |
| set nocompatible |
| // Place your settings in this file to overwrite the default settings | |
| { | |
| // Workbench Settings | |
| "workbench.activityBar.visible": true, | |
| "workbench.tips.enabled": false, | |
| "workbench.startupEditor": "none", | |
| "workbench.settings.editor": "json", | |
| "workbench.editor.highlightModifiedTabs": true, | |
| "workbench.editor.enablePreview": false, | |
| "workbench.colorCustomizations": { |
Before we start building LOTS and LOTS of Spring Boot based Cloudy Apps in 2019, let's go back to the books and (re)learn how to build them today. Remember, the last time we got into building Microservices it was 2015!
Bottomline, we need to build Spring Boot Seed App(s), AGAIN!
| code --install-extension 4ops.terraform | |
| code --install-extension akamud.vscode-theme-onelight | |
| code --install-extension akarlsten.vscode-snazzy-akarlsten | |
| code --install-extension alefragnani.project-manager | |
| code --install-extension alexanderte.dainty-vscode | |
| code --install-extension anotherglitchinthematrix.monochrome | |
| code --install-extension azemoh.one-monokai | |
| code --install-extension bierner.github-markdown-preview | |
| code --install-extension bierner.markdown-checkbox | |
| code --install-extension bierner.markdown-emoji |
Manual - By script
In machine A,
code --list-extensions | xargs -L 1 echo code --install-extension
copy and paste the echo output to machine B
sample output
Either copy the aliases from the .gitconfig or run the commands in add-pr-alias.sh
Easily checkout local copies of pull requests from remotes:
git pr 4 - creates local branch pr/4 from the github upstream(if it exists) or origin remote and checks it outgit pr 4 someremote - creates local branch pr/4 from someremote remote and checks it out
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: