mrnabati

Working with submodules in your repository

• Create the submodule:

  git submodule add -b master <git@github.com:MYSUBMODULE.git> <path/to/MYSUBMODULE>

  This creates the submodule and makes it track submodule's master branch. You can change the branch name if you want to track a different branch.

• Change some settings. In the parent repo:

  # make it so that git status will include changes to submodules.

mmckechney

{
	"properties": {
        "displayName": "Append NSG if missing",
        "description": "Sets default NSG if none is specified",
		"policyType": "Custom",
        "mode": "All",
        "parameters": {
            "nsgResourceId": {
                "type": "String",
                "metadata": {

srjha

image: atlassian/default-image:2

pipelines:
  # By default (master branch) only validation is going to be triggered
  default:
    - step:
        deployment: test
        name: EKS Infra build and validate
        script:
          - mkdir -p ~/bin

ismits

if (!someString?.trim()) {
    logger.lifecycle("the string is null or empty.")
}

joahking

(a gist based on the old toolmantim article on setting up remote repos)

To collaborate in a distributed development process you’ll need to push code to remotely accessible repositories.

This is somewhat of a follow-up to the previous article setting up a new rails app with git.

For the impatient

Set up the new bare repo on the server: