diff options
8 files changed, 202 insertions, 10 deletions
diff --git a/_tils/2020-11-12-git-bisect-automation.md b/_tils/2020-11-12-git-bisect-automation.md new file mode 100644 index 0000000..ff3ed34 --- /dev/null +++ b/_tils/2020-11-12-git-bisect-automation.md @@ -0,0 +1,33 @@ +--- + +title: Git bisect automation + +date: 2020-11-12 2 + +layout: post + +lang: en + +ref: git-bisect-automation + +--- + +It is good to have an standardized way to run builds and tests on the repository +of a project, so that you can find when a bug was introduced by using +`git bisect run`. + +I've already been in the situation when a bug was introduced and I didn't know +how it even was occurring, and running Git bisect over hundreds of commits to +pinpoint the failing commit was very empowering: + +``` +$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46 +$ git bisect start HEAD $GOOD_COMMIT_SHA +$ git bisect run sn -c './build.sh && ./run-failing-case.sh' +``` + +Git will than do a binary search between the commits, and run the commands you +provide it with to find the failing commit. + +Instead of being afraid of doing a bisect, you should instead leverage it, and +make Git help you dig through the history of the repository to find the bad code. diff --git a/_tils/2020-11-12-useful-bash-variables.md b/_tils/2020-11-12-useful-bash-variables.md index af83015..d0849ce 100644 --- a/_tils/2020-11-12-useful-bash-variables.md +++ b/_tils/2020-11-12-useful-bash-variables.md @@ -2,7 +2,7 @@ title: Useful Bash variables -date: 2020-11-12 +date: 2020-11-12 1 layout: post diff --git a/locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po b/locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po new file mode 100644 index 0000000..6aed806 --- /dev/null +++ b/locale/eo/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po @@ -0,0 +1,50 @@ +# +msgid "" +msgstr "" + +msgid "title: Git bisect automation" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: git-bisect-automation" +msgstr "" + +msgid "" +"It is good to have an standardized way to run builds and tests on the " +"repository of a project, so that you can find when a bug was introduced by " +"using `git bisect run`." +msgstr "" + +msgid "" +"I've already been in the situation when a bug was introduced and I didn't " +"know how it even was occurring, and running Git bisect over hundreds of " +"commits to pinpoint the failing commit was very empowering:" +msgstr "" + +msgid "" +"$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46\n" +"$ git bisect start HEAD $GOOD_COMMIT_SHA\n" +"$ git bisect run sn -c './build.sh && ./run-failing-case.sh'\n" +msgstr "" + +msgid "" +"Git will than do a binary search between the commits, and run the commands " +"you provide it with to find the failing commit." +msgstr "" + +msgid "" +"Instead of being afraid of doing a bisect, you should instead leverage it, " +"and make Git help you dig through the history of the repository to find the " +"bad code." +msgstr "" + +msgid "date: 2020-11-12 2" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/locale/eo/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po b/locale/eo/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po index c2b94f4..bcff15d 100644 --- a/locale/eo/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po +++ b/locale/eo/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po @@ -5,9 +5,6 @@ msgstr "" msgid "title: Useful Bash variables" msgstr "" -msgid "date: 2020-11-12" -msgstr "" - msgid "layout: post" msgstr "" @@ -86,3 +83,9 @@ msgid "" "read, I find those useful shortcut that are handy when writing at the " "interactive terminal." msgstr "" + +msgid "date: 2020-11-12 1" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/locale/fr/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po b/locale/fr/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po new file mode 100644 index 0000000..6aed806 --- /dev/null +++ b/locale/fr/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po @@ -0,0 +1,50 @@ +# +msgid "" +msgstr "" + +msgid "title: Git bisect automation" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: git-bisect-automation" +msgstr "" + +msgid "" +"It is good to have an standardized way to run builds and tests on the " +"repository of a project, so that you can find when a bug was introduced by " +"using `git bisect run`." +msgstr "" + +msgid "" +"I've already been in the situation when a bug was introduced and I didn't " +"know how it even was occurring, and running Git bisect over hundreds of " +"commits to pinpoint the failing commit was very empowering:" +msgstr "" + +msgid "" +"$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46\n" +"$ git bisect start HEAD $GOOD_COMMIT_SHA\n" +"$ git bisect run sn -c './build.sh && ./run-failing-case.sh'\n" +msgstr "" + +msgid "" +"Git will than do a binary search between the commits, and run the commands " +"you provide it with to find the failing commit." +msgstr "" + +msgid "" +"Instead of being afraid of doing a bisect, you should instead leverage it, " +"and make Git help you dig through the history of the repository to find the " +"bad code." +msgstr "" + +msgid "date: 2020-11-12 2" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/locale/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po b/locale/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po index c2b94f4..bcff15d 100644 --- a/locale/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po +++ b/locale/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po @@ -5,9 +5,6 @@ msgstr "" msgid "title: Useful Bash variables" msgstr "" -msgid "date: 2020-11-12" -msgstr "" - msgid "layout: post" msgstr "" @@ -86,3 +83,9 @@ msgid "" "read, I find those useful shortcut that are handy when writing at the " "interactive terminal." msgstr "" + +msgid "date: 2020-11-12 1" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/locale/pt/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po b/locale/pt/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po new file mode 100644 index 0000000..6aed806 --- /dev/null +++ b/locale/pt/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po @@ -0,0 +1,50 @@ +# +msgid "" +msgstr "" + +msgid "title: Git bisect automation" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: git-bisect-automation" +msgstr "" + +msgid "" +"It is good to have an standardized way to run builds and tests on the " +"repository of a project, so that you can find when a bug was introduced by " +"using `git bisect run`." +msgstr "" + +msgid "" +"I've already been in the situation when a bug was introduced and I didn't " +"know how it even was occurring, and running Git bisect over hundreds of " +"commits to pinpoint the failing commit was very empowering:" +msgstr "" + +msgid "" +"$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46\n" +"$ git bisect start HEAD $GOOD_COMMIT_SHA\n" +"$ git bisect run sn -c './build.sh && ./run-failing-case.sh'\n" +msgstr "" + +msgid "" +"Git will than do a binary search between the commits, and run the commands " +"you provide it with to find the failing commit." +msgstr "" + +msgid "" +"Instead of being afraid of doing a bisect, you should instead leverage it, " +"and make Git help you dig through the history of the repository to find the " +"bad code." +msgstr "" + +msgid "date: 2020-11-12 2" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/locale/pt/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po b/locale/pt/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po index c2b94f4..bcff15d 100644 --- a/locale/pt/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po +++ b/locale/pt/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po @@ -5,9 +5,6 @@ msgstr "" msgid "title: Useful Bash variables" msgstr "" -msgid "date: 2020-11-12" -msgstr "" - msgid "layout: post" msgstr "" @@ -86,3 +83,9 @@ msgid "" "read, I find those useful shortcut that are handy when writing at the " "interactive terminal." msgstr "" + +msgid "date: 2020-11-12 1" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" |