تدريب Shadowing: The easy way to keep your repos tidy. - تعلم التحدث بالإنجليزية عبر الفيديو

اختر وضع التدريب

كل وضع يفتح غرفة تدريب بملء الشاشة.

78 جمل

إذا كانت الجمل قصيرة أو طويلة جدًا، انقر على Edit لتعديلها.

Hello and welcome.

I'm James Murphy and today we're talking about PreCommit, which is a really cool tool that you can use to keep your codebase tidy

and catch some simple mistakes before things ever get committed into Git.

It happens.

There's a new person on your team that doesn't really know about PEP8, or you just forget to run your code formatter, or you just make a typo in a config file somewhere.

But at the time, you don't really notice, so you just go ahead and git commit.

Then either something breaks, or just the quality of your codebase has gone down just a little bit.

Well, a bad config you can fix, and code you can just reformat.

But still, wouldn't it be better if you could just catch those errors before the commit happens?

That's what pre-commit is for.

Here's the story of pre-commit.

Basically, git has a notion of what are called commit hooks.

These are things that happen either before you commit or just after you commit or when you push or when you pull, things like that.

Git will store this and a whole bunch of other information in the .git folder inside a directory.

Depending on your editor, this folder might be hidden, so just look out for that.

You might have to unhide it.

This hooks folder is where git stores all these different hooks.

The ones you see here are just samples.

If you were to get rid of that .sample on the end of the file name, then git would actually run that action at that corresponding So if I have a file named pre-commit,

then Git will run that script right before a commit happens.

But you don't need to go out and waste your time writing something like this yourself.

A lot of really good scripts have already been written.

The pre-commit project just makes it really easy to pick

and choose things that you want to check for your own code base.

Let's start simple.

All I want to do is make sure that before I commit anything, I run my code formatter on it.

Of course, I can just run the code formatter before I commit, but the point is I shouldn't have to remember to do that.

Why not just make it automatic?

Well, it's super simple to set up.

Open up your terminal and just pip install pre-commit.

Then, at the root of your project, just make a new file called .precommitconfig.yaml.

Then, it's just this easy to add automatic code formatting on every commit.

You specify precommit hooks by just giving a git repository.

In this case, I'm using GitHub, but you can actually use any git repository, even a local one.

You specify the git tag that it's going to use, and then some information about what command to run and what arguments to give it.

In this case, I'll be using black to do the actual code formatting.

Then you use pre-commit to install the githooks into your githooks folder.

Now if we go and look in our githooks folder, we see that we have this new pre-commit file.

Alright, now let's add our files to git, commit, and see what happens.

As you can see, it ran black and the commit failed because some modifications were made, and it's not going to commit anything automatically.

I can go and manually inspect the hello file and see that everything looks good, or just compare the diff like I normally would before a commit.

Note that these modifications to the hello file were made after the file was staged.

That means I need to git add this file again, or if something went wrong and I don't like the changes that were automatically made,

then I can git restore the file to go back to the way it was before.

In this case, I'm happy with the changes, so I will add and then try to commit again.

This time, since everything passed, the commit went through.

Note that some graphical editors like this one, PyCharm, have built-in Git support and they will automatically add tracked files when you try to commit.

So if that's the case then it might look more like this.

Here I have a spurious space in there and I'm going to go ahead and try and commit.

Then I try to commit and I see the commit failed and I can go to the console to see what errors.

I see that it deleted the extra space

and then I can just go ahead and click commit again and then this time it will succeed.

So what else can you do besides automatically formatting your code?

Well you can write your own commit hooks so you can pretty much do whatever you want, but there are a ton of really good ones already written on this website here.

Here are just a few of my favorites.

You can delete trailing whitespace, make sure a file is either empty or ends with a new line, make sure that any yaml files have valid yaml in them,

make sure you're not accidentally committing any really big files into your repository, and check for any spurious breakpoints that you forgot to delete before committing.

You can also run your linter like flake 8, you can reorder and standardize the order that your imports happen in, you can check for outdated syntax and replace it with its modern equivalent,

and this would also be a good place to run your type checker, like MyPy.

Pre-commit is most popular in the Python world, but it's not something that's just limited to Python.

There are premade scripts for doing things like running clang-tidy or clang-format, or some other code formatter for a different language.

You don't have to reinstall anything if you change the YAML file, just go ahead and commit.

We see the commit failed because of a MyPy error, telling us that we passed the wrong kind of argument to this function f.

Also note that most hooks will only run if an applicable file actually changed.

So it's not going to be reformatting code that it already formatted and hasn't changed.

Finally, there's the question of safety.

How safe is it to automatically run programs on your source code before committing them?

Well, this ultimately goes down to the project and whether or not you trust the project to do the right thing.

Of course, these little scripts can be written by anyone, so if they put something malicious in, then you're going to be out of luck.

You can fix a specific version or even a specific hash in the config file.

This helps mitigate things like what if this project gets hacked and an attacker uploads something malicious.

But as always, only use projects that you really trust.

As far as accidental errors go though, like what if black accidentally changed the meaning of the code?

Well, that's something that I haven't actually run into.

If something did go wrong, it would really be up to you to catch it in the git diff or by running tests.

Of course, for an accidental mistake, you can always revert using the git restore command that I talked about earlier.

Well, that's all I've got.

I hope this makes your repos better.

تنزيل التطبيق

كل ما تحتاجه للتحدث بطلاقة

تقييم النطق بالذكاء الاصطناعيتقييم كل جملة

تدريب IPAأتقن كل صوت

المفرداتابنِ رصيدك من الكلمات

لعبة المفرداتتعلّم أثناء اللعب

امسح رمز QR

Download on theApp Store Get it onGoogle Play

FOR YOU

فيديو موصى به

68 جمل

Your AI Agent Starts Every Session Like a New Hire - Killian Carlsen-Phelan, Sonar

Daily ConversationUniversity StudentsWorking Adults

185 جمل

Use these CSS features instead of JavaScript

Daily ConversationUniversity StudentsWorking Adults

المفردات وملاحظات التحدث لهذا الدرس

يحتوي هذا الفيديو على 78 جملة و1244 كلمة للتدرب على الترديد. مدة الكلام 5:52. يتكلم المتحدث بسرعة، نحو 212 كلمة في الدقيقة، لذا ستسمع كثيرًا من وصل الكلمات واختزال الأصوات. 80% فقط من الكلمات ضمن أكثر 3,000 كلمة شيوعًا في الإنجليزية، فالمفردات صعبة نسبيًا.

أهم المفردات في هذا الفيديو

15 كلمة من الفيديو تستحق التعلّم، مع النطق والمعنى:

الكلمة	النطق	المعنى
hook اسم	/hʊk/	خَطَّاف
folder اسم	/ˈfoʊldɚ/	مِلَفّ, مُجَلَّد
script اسم	/skɹɪpt/	كِتَابَة
delete فعل	/dɪˈliːt/	حَذَفَ
automatic صفة	/ˌɔː.təˈmæt.ɪk/	تِلْقَائِيّ, أُوتُوماتِيكِيّ
restore فعل	/ɹɪˈstoɹ/	اِسْتَعَادَ
install فعل	/ɪnˈstɔl/	رَكَّبَ
tidy صفة	/ˈtaɪ.di/	مُنَظَّم, نَظِيف
compare فعل	/kəmˈpɛɚ/	قَارَنَ
trail اسم	/tɹeɪl/	أَثَر
valid صفة	/ˈvælɪd/	شَرَعِيّ
notion اسم	/ˈnoʊʃən/	مَفْهُوم, تَصَوُّر
applicable صفة	/əˈplɪk.ə.bəl/	قابل للتطبيق
import اسم	/ˈɪm.pɔɹt/	وَارِدَات
upload فعل	/ˈʌpˌloʊd/	حَمّل

الأفعال المركبة التي ستسمعها

الكلمة	المعنى
go down فعل	نَزَلَ
go out فعل	خَرَجَ

نطق يحتاج إلى انتباه

يستخدم المتحدث 18 من الصيغ المختصرة، مثل don't, I'm, you're. انطقها بصيغتها القصيرة كما تسمعها.

أصوات “sh” و“zh”: modification /ˌmɑdɪfɪˈkeɪʃən/, malicious /məˈlɪʃəs/, notion /ˈnoʊʃən/, hash /ˈhæʃ/
الكلمات الطويلة — انتبه لموضع النبر: automatic /ˌɔː.təˈmæt.ɪk/, accidentally /ˌæk.sɪˈdɛnt(ə)li/, modification /ˌmɑdɪfɪˈkeɪʃən/, applicable /əˈplɪk.ə.bəl/, directory /dɪˈɹɛktəɹi/

كيف تتدرب بهذا الفيديو

استمع إلى الفيديو كاملًا مرة واحدة دون أن تتكلم، ودوّن الكلمات التي لا تعرفها.
ابدأ بسرعة 0.75×، وردّد جملة جملة، ثم عُد إلى السرعة العادية عندما يصبح الأمر سهلًا.
سجّل صوتك وقارنه بالأصل، مع الانتباه إلى كلمات مثل hook, folder, script.

القواعد في هذا الفيديو

أكثر التراكيب التي يستخدمها المتحدث، مع العبارات نفسها من الفيديو:

التركيب	في الفيديو
المبني للمجهول be + اسم المفعول — التركيز على ما يحدث لا على من يفعله	are called · might be hidden · been written
المضارع التام have/has + اسم المفعول — حدث ماضٍ ما زال له أثر الآن	has gone · have already been written · have built

ما هي تقنية التظليل الصوتي؟

التظليل الصوتي (Shadowing) تقنية تعلم لغة مدعومة علمياً، طُورت أصلاً لتدريب المترجمين الفوريين المحترفين. الطريقة بسيطة لكنها قوية: تستمع لصوت إنجليزي أصلي وتكرره فوراً بصوت عالٍ — كظل يتبع المتحدث بتأخير 1-2 ثانية. تُظهر الأبحاث تحسناً كبيراً في دقة النطق والتنغيم والإيقاع وربط الأصوات والاستماع والطلاقة.

تقنية الشادوينغ: اقرأ الدليل الكامل خطوة بخطوة →

تدريب Shadowing: The easy way to keep your repos tidy. - تعلم التحدث بالإنجليزية عبر الفيديو

اختر وضع التدريب

تنزيل التطبيق

GitHub Copilot now controls your command line...

The 7 Quality Control (QC) Tools Explained with an Example!

DRY Often Makes Your Code Worse

STOP Running Code On Your Computer

Did Anthropic Kill Git?

Go’s Big Mistake

LangChain in 5 Minutes (Explained Clearly)

Git Explained in 100 Seconds

How I deploy serverless containers for free

9 Insane Claude Mods I Already Can't live Without