CodeRabbit Announces $16M Series-A Funding Led by CRV!
CodeRabbit Announces $16M Series-A Funding Led by CRV!
DSOC R&Dã®å³¶ã§ããArcã°ã«ã¼ãã«ã¦R&Dã¨ã³ã¸ãã¢ãåãã¦ãã¾ãããã®è¨äºãç®åãã«R&D DevOpséä¿¡ã¨é¡ãã¾ãã¦ãArcã°ã«ã¼ãã®é¢ã ããå½ç¤¾R&Dã®ã¨ã³ã¸ãã¢ãªã³ã°ããããããããã¼ãã§é£è¼ãã¦ããäºå®ã§ããä¹ããæå¾ ã ç§ã¯éå»ã«æ è¡è¨ããæ¸ãã¦ãªã人ã§ãã*1*2ãä»åã¯åãã¦æè¡ãããè¨äºãæ¸ãã¾ããGitHubã®pull requestã¸ã®ã³ã¡ã³ãã§çºåããã¯ã¼ã¯ããã¼ ã GitHub Actions ã§ä½ãã¾ãã github.co.jp ä¸ã®ãããªã¤ã¡ã¼ã¸ã§ããã³ã¡ã³ãã«åå¿ãã¦ã³ã¡ã³ããè¿ãã¢ã¯ã·ã§ã³ãå®ç¾©ãã¦ãã¾ããæ¬è¨äºã¯ /deploy staging /deploy production ã®ãããªã³ã¡ã³ãã«ãã£ã¦ãããã¤ã«å©ç¨ãããã¨ã念é ã«ç½®ãã¦ãã¾ãã ã³ã¡ã³ãé§åã¯ã¼ã¯ããã¼ã®ã¤ã¡ã¼ã¸ ç§ã¯æè¿GitHub Actionsã«å ¥ãè¾¼ãã§ããã
GitHub Actionsã®å©ç¨éãã¾ã¨ããã§ã¯GitHub Actionsã®ä½¿ç¨éãGoogle Spreadsheetã«ã¾ã¨ããã¹ã¯ãªãããæ¸ãã¾ããã ãã®ã¨ãã¯åä½ç¢ºèªãã§ããã°ããã£ãã®ã§ãèªåã®Googleã¢ã«ã¦ã³ãã§èªè¨¼ãã¦æ¸ãè¾¼ã¿ãè¡ãã¾ããã ãããããã®ã¹ã¯ãªãããå®æçã«å®è¡ããã®ãé¢åã§ãã ããã§GitHub Actionsã®ã¹ã±ã¸ã¥ã¼ã«å®è¡æ©è½ã使ããæ¯æ¥ä½¿ç¨éãè¨é²ããè¨å®ãè¡ãã¾ããã ã¤ãããAPIãã¼ã使ãã®ã¯ãªã¹ã¯ãé«ãã®ã§ãGoogle Cloudã®Workload Identityé£æºã使ã£ã¦ã¢ã¯ã»ã¹ãã¾ãã Workload Identity é£æºã®æ§æ GitHub Actions ããã®ãã¼ãªãã®èªè¨¼ã®æå¹åãåèã«Google Cloudå´ã®è¨å®ãè¡ãã¾ãã è¨å®å 容ããã¼ã¸ã§ã³ç®¡çãããã®ã§ãè¨å®ã«ã¯Terraformã使ç¨ãã¾ãã æ
Renovateã¯ä¾åé¢ä¿ã®æ´æ°ãèªååãã¦ããããã¼ã«ã§ããæ¬è¨äºã§ã¯Renovateã®è¨è¨ææ³ãç¥ããã¨ã§ãRenovateãããä¸æã«éç¨ã§ããããã«ãªããã¨ãç®æãã¾ãã Renovateã¨ã¯Renovate ã¯Mend社 (æ§WhiteSource社) ãéçºããããªã¼ã®ä¾åé¢ä¿æ´æ°ãã¼ã«ã§ããpackage.jsonãªã©ã«æ¸ãããã©ã¤ãã©ãªãã¼ã¸ã§ã³ãå¤ãå ´åã«ããããã®ãã¼ã¸ã§ã³ãæ°ãããããããªå¤æ´ãpull requestã¨ãã¦èªåçã«ä½æãã¦ããã¾ãã Activate the repos you want to automate dependency updates for. Renovate will then create an onboarding pull request for each repo, with a preview of the actions
EngineeringSecurityBehind GitHubâs new authentication token formatsWe're excited to share a deep dive into how our new authentication token formats are built and how these improvements are keeping your tokens more secure. As we continue to⦠Weâre excited to share a deep dive into how our new authentication token formats are built and how these improvements are keeping your tokens more secure. As w
Go ã§æ¸ãã CLI ãã¼ã«ã®ãªãªã¼ã¹ã¯ GoReleaser 㨠GitHub Actions ã§å人çã«ã¯æ±ºã¾ã February 4, 2020 lt;dr GoReleaser 㨠GitHub Actions ã使ãã¨ç°¡åã«ãã«ããããã¤ããªãä½ã£ã¦ã¢ãããã¼ãã§ããã 2ã¤ã® YAML ãæ¸ãã¦ãªãã¸ããªã«ã³ããããã .github/workflows/release.yml .goreleaser.yml git tag ã㦠push ãã ãã¤ããªããªãªã¼ã¹ããã å°ç¨ã®ãã¼ã«ããã¼ã«ã«ã«ã¤ã³ã¹ãã¼ã«ããå¿ è¦ã¯ãªãã æ¬é¡ åã«ãGo ã®ã³ãã³ãã©ã¤ã³ãã¼ã«ãç°¡åã«ãªãªã¼ã¹ãã | tellme.tokyo ã¨ããããã°ãæ¸ããã ããããããã£ã¨æ¥½ã«ãªã£ãã®ã§ç´¹ä»ããã åºæ¬çã«ãã®ãã¼ã¸ã§ç´¹ä»ããæ¹æ³ã§ã¯ 2 ã¤ã® YAML ããªãã¸ããªã«ç½®ãã ãã§çµããã ãã¼
GitHub's Google Cloud Build integration does not detect a cloudbuild.yaml or Dockerfile if it is not in the root of the repository. When using a monorepo that contains multiple cloudbuild.yamls, how can GitHub's Google Cloud Build integration be configured to detect the correct cloudbuild.yaml? File paths: services/api/cloudbuild.yaml services/nginx/cloudbuild.yaml services/websocket/cloudbuild.ya
GitHubã®IssueãNuxtã¨Netlifyã§ããã°åããã¨ããã®ããã£ã¦ã¿ãã®ã§è§£èª¬ãã¾ãã ãã¢ãµã¤ãï¼ https://gh-blog.netlify.com/ Issuesï¼ https://github.com/miyaoka/gh-blog/issues Headless CMS ã¯ããã«Headless CMSã«ã¤ãã¦è§£èª¬ãã¦ããã¾ããæ§æ¥ã®APIç¡ãã®WordPressã®ãããªä¸ä½åCMSã§ã¯ãªããã³ã³ãã³ã管çé¨åãåãé¢ãã¦APIã§ããã¨ãã§ããããã«ããã®ãHeadlessãªCMSã§ããããã«ããããã³ãã®å®è£ ããããã¤ãççµåã«ãªãã好ãã«ã§ããããã«ãªãã¾ãã ä¾ã¨ãã¦CMSã«Contentfulããããã¤ã«Netlifyã使ãæ§æã ã¨ãããªæãã«ãªãã¾ãã åèï¼ æ¬¡ä¸ä»£Headless CMSãcontentfulãäºå§ã - Qiita Nuxt.js
Steven J. Vaughan-Nichols ï¼ZDNET.comï¼Â ç¿»è¨³æ ¡æ£ï¼Â ç¢åç¾ç»é åæ¦ç¨å¤«Â ï¼ã¬ãªã¬ãªï¼ 2018-03-08 11:45 ãªã¼ãã³ã½ã¼ã¹ã®ã©ã¤ã»ã³ã·ã³ã°ã¯è¤éåããå ´åããããæè¿ã§ã¯ãå¤ãã®ããã°ã©ã ã¯8å²ãå ãããããªã¼ãã³ã½ã¼ã¹ã®ã³ã¼ãã§ãããã«2å²ã®ãªãªã¸ãã«ã³ã¼ãã追å ãããã®ã«ãªã£ã¦ããããã ããã®çµæçããã©ã¤ã»ã³ã·ã³ã°ã®è¤éåã«å¯¾å¿ã§ãããããGitHubã¯ããªã¼ãã³ã½ã¼ã¹ããã¸ã§ã¯ãã®ã©ã¤ã»ã³ã·ã³ã°æç¶ãã®ä¸é¨ãèªååããã®ã«ä½¿ã£ã¦ãã社å ãã¼ã«ãLicensedãããªã¼ãã³ã½ã¼ã¹åããã ã©ã¤ã»ã³ã¹ã«å¯¾ããGitHubã®æ¾ä»»ä¸»ç¾©çãªå§¿å¢ã®ãããã§ãã»ãã®æ°å¹´åã«ã¯GitHubã®å ¨ããã°ã©ã ã®ãã¡77ï¼ ã«æ示ãããã©ã¤ã»ã³ã¹ããªãã¨ã®èª¿æ»çµæããã£ããã¨ãèããã¨ãæå¿ã§ããåãã ããããã®ãã¨ãéè¦ã ã¨æããªããªããããã°ã©ã ãååå
çªç¶ã§ããï¼Goã§ã³ãã³ãã©ã¤ã³ãã¼ã«ãæ¸ãæï¼ãã¼ã«ã®é å¸ã¯ã©ããã¦ããã§ããããï¼ go get ã§ã¤ã³ã¹ãã¼ã«ã§ããããã«ãã GitHub ä¸ã«ãªãªã¼ã¹ãã¦ï¼ãã¦ã³ãã¼ããã¦ä½¿ã£ã¦ããã ã·ã¹ãã ã®ããã±ã¼ã¸ããã¼ã¸ã£ï¼Homebrew ãªã©ï¼ã使ã ãªã©ãã¡ã¸ã£ã¼ãã¨æãã¾ãï¼ ãã ï¼ãããã®é¸æè¢ã¯ã©ããåé¡ãããã¾ãï¼ go get -u ã¯å¸¸ã«ãªãã¸ããªã® HEAD ãã¤ã³ã¹ãã¼ã«ãã¦ãã¾ãããï¼ã¦ã¼ã¶ãã¤ã³ã¹ãã¼ã«ããã¿ã¤ãã³ã°ã«ä¾åãããã¤ããªãã§ãã¦ãã¾ãã¾ãï¼ãããé¿ããã«ã¯ dev ãã©ã³ããåã£ã¦ãã£ã¡ã§éçºããå¿ è¦ãããã¾ããï¼Go ã®ãã¼ã«ã¯ãããªã£ã¦ãªããã®ãå¤ãï¼ã©ã®ã¿ã¤ãã³ã°ã§ go get -u ãããè¯ããã¦ã¼ã¶ã«ã¯å®¹æã«å¤æã§ãã¾ããï¼ã¾ãï¼ä»®ã« dev ãã©ã³ãéç¨ããã¨ãã¦ãä¾åã©ã¤ãã©ãªã®æ´æ°ã®ã¿ã¤ãã³ã°ã¯å¶å¾¡ã§ããï¼vendoring ãª
GitHubã§ãã«ãªã¯ã¨ã¹ãåæã®éçºããã¦ããã¨ãgit blameã§ããªãããã®ã³ã¼ãããããªã£ã¦ããã®ãã調ã¹ãéã«ãcommit idã§ã¯ãªããã«ãªã¯ã¨ã¹ãã®çªå·ã表示ãã¦ã»ãããªãã¾ãã ã¨ããããã§æ¸ããã®ã git-blame-pr.plã 以ä¸ã®ãããªæãã§è¡¨ç¤ºãããã®ã§ã調æ»ãã¯ãã©ãã¾ãã $ git-blame-pr.pl lib/core/request.c (ä¸ç¥) PR #446 PR #606 h2o_iovec_t h2o_get_redirect_method(h2o_iovec_t method, int status) PR #606 { PR #606 if (h2o_memis(method.base, method.len, H2O_STRLIT("POST")) && !(status == 307 || status == 308)) PR
example.md Using <details> in GitHub Suppose you're opening an issue and there's a lot noisey logs that may be useful. Rather than wrecking readability, wrap it in a <details> tag! <details> <summary>Summary Goes Here</summary> ...this is hidden, collapsable content... </details> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details A collapsible section with markdown Click to expand!
TL;DR GitBucket 㨠Jenkins ã®é£æºã¯ã¨ã¦ãç°¡åãªã®ã§ããã2017/3/æ«ãªãªã¼ã¹ã®GitBucket ã® 4.11ï¼ãã5.0ããï¼ï¼ ãå¾ ã£ã¦ãã ããã GitHub Oraganization Folder ã使ã£ãè¨å®ããã¦ãã㨠ãªãã¸ããªã« Jenkinsfile ãç½®ãã ã㧠GitBucket - Jenkins ã®é£æºãå ¨é¨èªåçã«è¨å®ããã¾ãã 注æ ãã®è¨äºã¯GitBucketã®æªãªãªã¼ã¹ã®æ©è½ã«ã¤ãã¦æ¸ãã¦ãã¾ããä¸æãããã°2017/3/æ«ã«ãªãªã¼ã¹ããã4.11(?)ã«å«ã¾ããè¦è¾¼ã¿ã§ãã Jenkins ã® GitHub Branch Source Plugin ãã¼ã¸ã§ã³ 2.0.0 以éï¼ï¼ï¼ã§ GitHub API ã®ä½¿ãæ¹ã大ããå¤æ´ã«ãªããGitBucket 4.10 ã¾ã§ã® API å®è£ ã§ã¯å¯¾å¿ã§ãããJenkins å´ã§
tl;dr GitHubä¸ãããã¡ã¤ã«ä½æã§OK åç½®ã GitHubã§ãªãã¸ããªãä½ã£ãç´å¾ã¯READMEãLICENCEãä½æãããªã³ã¯ãåºã¦ãã¦ãããæãã«ãã³ãã¬ã¼ããé¸æãããã¨ãã§ãã¾ã ãã ãä¸åº¦ãã¡ã¤ã«ããªãã¸ããªã«ã³ããããã¦ãã¾ãã¨ãã®ãªã³ã¯ãåºãªããªã£ã¦ãã¾ãã¾ã LICENSEãæåã«ä½ãå¿ãã¦å¾ãã追å ãããã£ã¦ãã¨ãèªåã®å ´åããããã®ã§ããæ軽ã«ä½ãæ¹æ³ãå¶ç¶çºè¦ããã®ã§æ¸ãã¾ã ããæ¹ ããã㧠Create new file ãã¯ãªãã¯ããå¾ã« ãã¡ã¤ã«åãå ¥åããã ãã§ããLICENSEã .gitignore ã£ã¦ãã¡ã¤ã«åãå ¥åããç¬éãã³ãã¬ã¼ãé¸æã®ãã«ãã¦ã³åºã¦ãã¾ã ã¦ã£ããä»ã¾ã§æ°ãããªãã¸ããªä½ã£ãç´å¾ã«ãããã³ãã¬ã¼ãããä½æã§ããªãã¨æã£ã¦ããããã
ã¿ãªãããé£æ¥ GitHub ããã©ã¦ã¸ã³ã°ãã¦ãã¨æããã§ãããããå¿«é©ã«ãã©ã¦ã¸ã³ã°ã§ããæ¡å¼µæ©è½ãç´¹ä»ãããã¨æãã¾ãã
ããæ¥ã PR ã®å 容ãè¦ãã«ãã¼ã¸ãããã¨ã岡島ï¼ãããã£ã¼ã®ï¼ã¨ããããããç¬ã£ãâ ãã®ãã (@a_know) 2015, 9æ 10 ã¨ãããã¨ã§ãè³å¤©æ°ã«ç¬ã£ã¦ãããã @a_know ãããã¤ãããªmasterãªãã¸ããªã«ç´æ¥pushãããã¿ã¼ã³ã§ããï¼â ãã¼ã ãï¼ å代ALF (@soudai1025) 2015, 9æ 10 ã¨ãã話ã«ãªããããã¦ãªãã ãã @a_know push -fã¨åæ§ãGitã®éç¨ã¢ã³ããã¿ã¼ã³ã¨ãã©ããã«çºããã»ããã§ããã¼ãã#ããã°å¾ ã£ã¦ã¾ãâ ãã¼ã ãï¼ å代ALF (@soudai1025) 2015, 9æ 10 ã¨ããã¯ãªãã«ãªã£ãã®ã§ãæ¬å½ã«å¿ è¦ã¨ãã¦é ãã¦ããã®ãã©ããã¯ã¨ãããã Git / GitHub ã§ã¼ããã¼ãã®è·å ´ã§æ°ãã¤ãã¦ããããªãã¨ãã¾ã¨ãã¦ã¿ãã ããã ããã GitHub Flow ã«æ²¿ã£ã¦éçºãã åºæ¬
The more we write about the inner turmoil, the more people step forward to share details and opinions. We're hearing these themes repeatedly: Cofounder CEO Chris Wanstrath, with support from the board, is radically changing the company's culture: Out with flat org structure based purely on meritocracy, in with supervisors and middle managers. This has ticked off many people in the old guard.Its on
ãç¥ãã
é害
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}