I have only one that I use all the time "rcheckout". Since I use gitlab and it allows the creation of branches with a title like "ISSUE_NR-ISSUE_TITLE" I can do git rcheckout ISSUE_NR and checkout that branch without having to type the full title. I don't know where I got this from originally.
#!/bin/bash
git fetch
[ ${#} -ne 1 ] && { echo -e "Please provide one search string" ; exit 1 ; }
MATCHES=( $(git branch -a --color=never | sed -E 's|^[* ] (remotes/origin/)?||' | sort -u | grep -E "^((feature|bugfix|release|hotfix)/)?([A-Z]+-[1-9][0-9]*-)?${1}") )
case ${#MATCHES[@]} in
( 0 ) echo "No branches matched '${1}'" ; exit 1 ;;
( 1 ) git checkout "${MATCHES[0]}" ; exit $? ;;
esac
echo "Ambiguous search '${1}'; returned ${#MATCHES[@]} matches:"
for ITEM in "${MATCHES[@]}" ; do
echo -e " ${ITEM}"
done
exit 1
I trying to create a management software for Integral Coops in Portugal. In a gross oversimplification Integral coops tend to be location based and allow freelancers and small groups to come together and have a infrastructure as if they were a big business while keeping their independence on the work they want to do
I'm trying to make it: a collective project shared between multiple coops, open source, sustainable in the long term.
I've already did some micro projects to the coop I'm a part of, like changing the workflow of expense invoice management from a totally manual process to an 80% automated process so I'm pretty sure I can provide significant benefits to the coops. Right now There's already a prototype andI'm in the process of talking with cooperatives finding financing and making it real.
website is at https://coops.pt (very early stages, in portuguese)
I'm the person that was copy-past school work in the 90's for things that I wasn't interested in.
I'm also the person who spent years learning things that I was passionate for without a end goal in mind.
The issue here is not AI, it's motivation.
Maybe that's because of much I learned about about color, but I very quickly get to a point where the correct answer can only be 50% blue, 50% green. Answering either blue or green feels wrong to me.
I have a very unscientific feeling that the scientific consensus will probably one day end up being something like:
sun is good for you in moderation, the amount that is ok depends on your skin color, how tanned you get, in which part of the world you are and how often you are outside. Avoid too much sun and avoid sun burns and also avoid crazy strong sunscreens that block the benefits of getting sunlight. The lifestyle that some people have of spending the whole year inside in an office and that spending their all vacations roasting at the beach is very unhealthy because body does not have time to adapt.
It's also known that sun exposure causes the vast majority of visible skin aging.
So I choose to use overkill sunscreen on my face and neck to preserve my youth and balance that out by using no sunscreen on my legs.
In the summer, running around in shorts, I should get plenty of sun.
In the winter, I supplement vitamin D anyway
- We need to control our own destiny and not get locked into a closed vendor.
- We need to protect our data.
- We want to invest in the ecosystem that’s going to be the standard for the long term.
Thank you Meta for being the bright light of ethical guidance for us all.
#!/bin/bash git fetch
[ ${#} -ne 1 ] && { echo -e "Please provide one search string" ; exit 1 ; } MATCHES=( $(git branch -a --color=never | sed -E 's|^[* ] (remotes/origin/)?||' | sort -u | grep -E "^((feature|bugfix|release|hotfix)/)?([A-Z]+-[1-9][0-9]*-)?${1}") ) case ${#MATCHES[@]} in ( 0 ) echo "No branches matched '${1}'" ; exit 1 ;; ( 1 ) git checkout "${MATCHES[0]}" ; exit $? ;; esac echo "Ambiguous search '${1}'; returned ${#MATCHES[@]} matches:"
for ITEM in "${MATCHES[@]}" ; do echo -e " ${ITEM}" done exit 1