Liferay Digital Experience Platform VS hub

One of the most interesting points from the conversation was about something also encouraged here at Liferay: exchanging roles and teams. I, for one, changed teams many times. It happens both at bxblue and Red Hat. - Source: dev.to / 4 months ago

Traditionally, it is considered good practice to comment code. However, this wisdom has been revisited in recent times. At Liferay, for example, we follow a policy of not commenting code. Personally, I am an enthusiast of this philosophy. But I don't want to present or defend this strategy here, there is a lot of good material on this subject. I want to discuss an open question. - Source: dev.to / 7 months ago

Use hub here via CLI and forget the gui https://hub.github.com/. - Source: Hacker News / 8 months ago

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities. - Source: dev.to / 11 months ago

Parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name ... Source: almost 2 years ago

You can always query via github api or use the hub client (from their home page https://hub.github.com/). Source: over 2 years ago