common workflow in oss contributions is fork → edit → pr
when making repeated contributions, the master
branch of the fork needs to be in sync with the original – the upstream
and here's one way to do that
noun hy·dra re·po
- a version controlled repository of code whose default branch is an insignificant tail that links to multiple heads that are branches of equal importance
- a single repo of multiple components because original author didn't want folders nor separate repos
- a single repo documenting the same thing in different {human, computer} languages, tones, etc.
- I haven't thought of any more.
The software is implemented using JavaScript frameworks and Firebase. The Javscript frameworks, React and Express, are used for the frontend and backend respectively. Firebase is used for the authorization of users, sending and accepting friend requests, creating rooms to chat with other individuals and most importantly playing virtually with other users using Firebase Authentication, Firestore and Cloud Functions. With regards to the working of the gyration board, the fronted and backend are constantly in communication with each other from the time the device is turned ON. Express reads the signals from the Raspberry Pi, performs calculations as required and sends the data to the React frontend. Arrows indicating the position where the user should place their feet, and the scores of the user are displayed on a display device throughout the game.
prepend_to_path(){ | |
for dir in "${@}"; do | |
if [ -d "${dir}" ]; then | |
PATH="${dir}:${PATH}" | |
fi | |
done | |
} | |
append_to_path(){ | |
for dir in "${@}"; do |