nikhita

Open source beginner bugs

This is a list of JavaScript projects on Github that label issues as easy or beginner-friendly.

• beginner
  • eslint/eslint
  • mozilla/pdf.js
  • TryGhost/Ghost
  • AnalyticalGraphicsInc/Cesium
  • larvalabs/pullup

nikhita

/*
* Note: This template uses some c++11 functions , so you have to compile it with c++11 flag.
*       Example:-   $ g++ -std=c++11 c++Template-Codejam.cpp
*
* Author : Akshay Pratap Singh
* Handle: code_crack_01
*
*/

/********   All Required Header Files ********/

nikhita

diff --git a/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/deepcopy.go b/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/deepcopy.go
index b865f3f746..8d961ce477 100644
--- a/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/deepcopy.go
+++ b/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/deepcopy.go
@@ -23,17 +23,19 @@ func (in *JSONSchemaProps) DeepCopy() *JSONSchemaProps {
 	}
 	out := new(JSONSchemaProps)
 
-	if out.Default != nil {
+	*out = *in

nikhita

'use strict';

const fs = require('fs')
const http = require('http')

const K8S_HOST = process.env['K8S_HOST'] || '10.100.0.1'
const K8S_SECRET = process.env['K8S_SECRET'] ||
  fs.readFileSync('/var/run/secrets/kubernetes.io/serviceaccount/token', 'utf-8')

var req = http.request({

nikhita

#!/bin/bash -ex

rm -rf cache.new
if [ ! -d cache ]; then
    mkdir cache.new
    pushd cache.new
    for repo in $(ls -1 ../kubernetes/staging/src/k8s.io); do
	git clone git@github.com:kubernetes/${repo}.git
    done
    popd

nikhita

[merge]
tool = mymeld
conflictstyle = diff3

[mergetool "mymeld"]
# Shows three-pane merge view with central output directly being the merged file to save
cmd = $MANISHMELD $LOCAL $BASE $REMOTE --output=$MERGED
#cmd = meld "$LOCAL" "$BASE" "$REMOTE"

nikhita

Check broken links in Kubernetes Community repo

To help the community and make sure that all documentation is up to date and correct, a very important role to play is to make sure all links are working correctly.

To do this, you can use simple tools such as markdown-link-check.

Setup

1. Install markdown-link-check.

nikhita

You need the rights to reopen pull requests on the repository.

1. Write down the current commit hash of your PR-branch git log --oneline -1 <PR-BRANCH>
2. Write down the latest commit hash on github before the PR has been closed.
3. git push -f origin <GITHUB-HASH-FROM-STEP-2>:<PR-BRANCH>
4. Reopen the PR.
5. git push -f origin <HASH-FROM-STEP-1>:<PR-BRANCH>

Example

You've a PR branch my-feature currently at 1234567. Looking at the the PRs page, we see that the PR was closed when my-feature pointed at 0abcdef.