Today I stumbled upon having to know if a specific commit was present or not in the release branch. I of course checked stackoverflow, i didn’t have it right in my mind.

VERSION=2.4
COMMIT_HASH=123acaef123acaed
git log origin/release/$(VERSION) | grep $(COMMIT_HASH) | wc -l

1. git log - that’s I assume it is ok, just checking the origin branch
2. grep - also I think that’s ok, just finding the commit hash from the git log list
3. wc -l - stands for word count and is a command-line utility that counts the number of lines, words, characters, and bytes in a file. and -l flag tells wc to count only the number of lines.

and there you go! You have effortlessly checked if your commit was present in a specific remote branch

These days I was working on making the iOS application complaint to the new EU regulations for accessibility. With a proper auditory of the app, it is rather easy to implement a better accessibility.

However I must say, until this momentm I did not find ANY testing framework that actually covers accessibility as it is required by law.

We have AccessibilitySnapshot that is very limited, we also have ViewInspector which you can try to guarantee certain attributes. But I couldn’t find a framework that would tell me: hey you are not doing it right, group these elements, this and that should have a different accessibilityTrait etc. (In fact there is one, but I am not mentioning because it relies on ui-test and on top of that it did not find any really useful issue).

Finally! It is there and alive! This blog is now fully functional without the limitations of github-pages gem. But hey! How did I even do that? Can I still remember it? Let’s see the digested steps:

This is it! The very first initial commit of all: hello world. To be very clear this blog is going to help me to keep on track, to learn new things, and also to not forget them. But, if you want learn together, let’s go then!