投稿時間:2023-05-01 11:11:31 RSSフィード2023-05-01 11:00 分まとめ(11件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
js	JavaScriptタグが付けられた新着投稿 - Qiita	お母さんでもわかるReact「_app.js」	https://qiita.com/pix_shimitomo/items/424c9a1e4a5cfb23317c	appjs	2023-05-01 10:36:50
js	JavaScriptタグが付けられた新着投稿 - Qiita	TanStack Query（旧React Query）を使ってみた	https://qiita.com/nanndot/items/1102bc784934fcd8ac5d	reactquery	2023-05-01 10:17:03
AWS	AWSタグが付けられた新着投稿 - Qiita	初心者が初心者のためにCloudFrontをまとめてみた	https://qiita.com/Yona_Sou/items/80954f254ba5a5b6d696	cdncontentdeliverynetwork	2023-05-01 10:03:44
Docker	dockerタグが付けられた新着投稿 - Qiita	【Road to Cassandra Day】Cassandra学習環境を準備する	https://qiita.com/yoshiyuki_kono/items/6bbad8705aa6a59adfcd	cassandra	2023-05-01 10:52:28
技術ブログ	Developers.IO	[小ネタ] ECS でタスクの作成時刻を確認する方法	https://dev.classmethod.jp/articles/ecs-how-to-check-task-creation-time/	amazon	2023-05-01 01:34:04
海外TECH	DEV Community	Git Commit Like A Pro	https://dev.to/stephikebudu/git-commit-like-a-pro-56d8	Git Commit Like A ProVersion control systems make collaboration seamless in software development Git is a version control system used for source code management It is amongst others not only the most popular among developers but offers excellent features to help in the tracking and managing of software Git interacts with software using specific commands via the command line interface to perform various tasks ranging from initializing a git repository to keeping track of every step of the development process In this article some important git commands including git init git add and git commit will be explained with an emphasis on git commit GIT INITThis command is used to initialize a git repository which is basically telling git to keep track of the repository to “keep an eye out for changes in the repository This is the first step to managing source code with git The syntax for this is git init lt repository name gt GIT ADDThis command is used to track file s in the git repository This command tells git to take record of specific file s for the next commit Git takes a snapshot of the file s pending the next commit only file s succeeding this command will be recorded by git The syntax for this is git add lt file name gt or git add Using the period symbol in place of file name tracks all files instead of a single file This is preferred in instances where tracking multiple files is needed instead of having to repeatedly run a single command with the different file names or type out multiple file names git add is more efficient GIT COMMITThis command is used to save the recorded changes made using the git add command This command however takes at least two additional arguments The most common syntax for this is git commit m “write commit message here The m flag means message which is recorded in the quotation marks that comes right after the flag It is important to note that the commit message should always be written in the imperative form that is statements that gives a command or makes a request from the reader This would be a quick way to make a commit but there are times when a more detailed commit message is needed beyond a simple statement CRAFTING GREAT GIT COMMIT MESSAGEAn effective git commit message consists of the right amount of information written properly Conventional commits defines the specification that provides easy rules for creating useful commit history that makes it easy for you your project collaborators and or git as the case may be to understand and possibly perform tasks with your git commits These specifications automatically generate change logs can help determine semantic version bumps based on your commit and establish a properly structured commit history Some benefits of properly structuring a git commit are It makes debugging easier using commit history It helps a developer contribute meaningfully to open source software It makes collaboration easier and enables better use of even more git commands like git reset git revert and so on It identifies a developer as a good collaborator as a good commit message saves project maintainer time because pull requests are clearer and faster to review Any git commit message can be split into five as specified by conventional commits The syntax for this is lt type gt optional scope lt description gt optional body optional footer s lt type gt This is the first part of a commit message and is used to communicate the intent of your change This usually takes the value fix for when the commit addresses a bug feat for when the commit includes a feature you worked on build chore style refactor test ci or docs as the case may be optional scope This is the second part of the commit message it provides additional information to the lt type gt value passed Best practice for writing the scope is usually a noun surrounded by parentheses eg feat user introduce anonymous comment feature You can also indicate if this commit type contains and change that may break the code by using an exclamation mark after the closing parenthesis and before the colon This part of a commit message is optional lt description gt The third part of the commit message is the description which is what is written in a one liner git commit message using the m flag The description should be written in the imperative form a great test for the imperative form of a commit message will be to insert it in this phrase “When implemented this commit will The sentence should be grammatically correct if the commit message is in the imperative form It should be short and precise This part of the commit message is in actual sense the commit title optional body The fourth part of the commit message is an optional body which further explains the commit description it follows the commit title with one blank line This is optional as well as not all commits are complex that they require further description Additionally the git commit rule suggests that the lt description gt is limited to characters while the optional body should wrap at characters optional footer s The fifth part of a commit message is the footer It is usually separated from the body by one blank line and contains an issue tracker The footer is optional as well considering not all commits are directly addressing an issue and need to reference and issue ID This section can also be used to document metadata options eg indicating what method you used for development Run git commit in the command line interface without any argument to prompt the git commit message full edit mode A common confusion around making a git commit is how often to make a commit which raises the question how much change deserves its own commit The best opinion I ve come across so far concerning this is that a unit of functional change is equivalent to a single commit This way you can easily reverse to a previous version of the code without doing any serious “damage The git commit command is flexible enough to take a variety of flags and even a combination of flags to perform various tasks Some other git commands can give insight using the git commit command Some useful related git commit commands are git commit v this commands shows the status of files which ones have or haven t been staged for commit as well as gives an insight or context to what the content of the commit should be git commit ーamend this command is used to add newly tracked files to the previous commitgit commit ーamend v this command is used to add newly tracked files to previous commit and have a detailed view of what is being added to the previous commit the commit message of the previous commit can be updated using this command git commit ーamend ーno edit this is used to add new files to previous commit without changing the commit message git show this is used to view the latest commits git log this displays all the commits for the current working repository this can take additional flags like ーoneline ーstat or ーpatch to display more specific information about the commit history git blame this is used to view the changes in a file line by line as well as see who changed what You can read more on Conventional Commits here	2023-05-01 01:16:10
金融	ニッセイ基礎研究所	米個人所得・消費支出（23年3月）－PCE価格のコア指数は高止まり	https://www.nli-research.co.jp/topics_detail1/id=74684?site=nli	月の名目個人消費前月比は、財消費が前月と前月からマイナス幅が拡大した一方、サービス消費は前月と伸びが加速した図表。	2023-05-01 10:03:13
金融	ニッセイ基礎研究所	確定拠出年金やNISAでは何に投資したら良いのか【2023年３月版】－国内債券型、国内株式型、外国株式型等でパフォーマンスを比較してみた	https://www.nli-research.co.jp/topics_detail1/id=74672?site=nli	目次はじめにー年月末から年月末まで直近か月間の各資産の価格推移ー代表的な金融危機直前から年月末まで毎月万円を積立投資したらいくらになるのかー長期投資ではリスクよりリターンが大切である理由・リターンとリスクの基本概念・投資期間ごとの累積リスクと年平均リスクの関係・投資期間とリターンとリスクの関係ー若い人は短期的な値動きをあまり気にせず、積極的にリターンが高い資産に投資すべきである・残りの投資期間が長い若い人が考えるべきこと・残りの投資期間が短い人が考えるべきことー結論年夏に「老後資金万問題」で取り上げられたように、公的年金だけでは老後の生活を安心して送ることが出来ないということが広く認識されている。	2023-05-01 10:51:12
ビジネス	ダイヤモンド・オンライン - 新着記事	ハイテク分野の収入トップはスタンフォード大卒業生 - WSJ発	https://diamond.jp/articles/-/322475	収入	2023-05-01 10:15:00
IT	週刊アスキー	"飛ぶように売れるおはぎ"の名店「さいち」とチロルチョコがコラボ！ まごころこもった味を1粒に【東北エリア限定】	https://weekly.ascii.jp/elem/000/004/134/4134246/	東北地方	2023-05-01 10:45:00
海外TECH	reddit	The Boston Bruins have been eliminated from the Stanley Cup Playoffs after losing to the Florida Panthers in 7 games	https://www.reddit.com/r/hockey/comments/1349hnf/the_boston_bruins_have_been_eliminated_from_the/	The Boston Bruins have been eliminated from the Stanley Cup Playoffs after losing to the Florida Panthers in games submitted by u EliminatorBot to r hockey link comments	2023-05-01 01:51:29