Open StephCurry07 opened 1 year ago
URL of Forked Repo: https://github.com/StephCurry07/scaler-open-source-september-challenge Screenshot of cloned Repo:
All local branches:
Updated and Synced contents in local repository:
CLI Commands:
Before Reset:
After Reset:
Pushed after rebase
Commands:
Merge Editor:
Commit History:
Updated the whole branch with the main repository... Then Added challenger and resolved a merge conflict
Pushed:
Merge Conflict
Resolved
Merged Conflicts using Git and code editor
Conflicts:
Resolved:
Final:
Learnt GitHub Desktop...felt bulky earlier when I tried to learn. Now it has improved. Did basic commands created branch tried a few things, felt it was a good tool if you don't want to write the commands over and over. But still dev experience and fun comes from cli only
GitHub Codespaces:
GitHub codespaces is a good initiative to make the code or repository more interactive as it has VSCode Integration and we can also install any extensions related to the repository. Terminal isn't much different. Further it feels more powerful as a developer to use a tool like this instead of coding locally. Every functionality can be achieved here compared to the local system. A few consequences would be that it requires internet connectivity. It can incur costs as it uses cloud. My experience overall was good and I am excited to use it more effectively in the future.
At a high level, GitHub Actions can automate any webhook on GitHub—and that makes it a powerful and flexible platform feature that’s able to handle complex workflows and operations or do something as simple as send a Slack message to someone when a pull request is ready to review. It feels cool using CI/CD kind of features
Project Boards
Project created and cards created:
Task moved
Creating and seeing the aliases, Running alias command(1)
Running the command with alias(2)
Challenge 24: Today's task was to read about how to actually contribute to open source, what are the best practices when you are actually contributing. That included naming conventions for branches and how to make a good PR and which issues to work upon based on the labels. Feeling excited for the next challenge
Today I looked for some github repositories having good first issues, tried to analyze what exactly do we have to do, and searching for a good project in which i can try contributing something. I searched a lot but couldn't find any repo in which my skillset matches it, luckily found one on the https://goodfirstissue.dev/ site, searched for a good first issue and commented on it. I'll look more into it and try contributing to open source.
This is the link of the repo and issue : https://github.com/LangTrans/LangTrans/issues/4
Today, I researched more and found more repositories and projects to contribute to, I'm getting an understanding bit by bit of what and how to do. I looked up issues on a few repos such as git-cola, nalgebra, SeaQL etc. but I'm finding their level hard as epr my current knowledge. Its hard to understand the issues and looking their whole codebase to exactly understand the problem... Progressing bit by bit till I find a project that's suitable for me or rather make myself suitable for the project :).
Pick specific commits and change them in the new branch
Usage:
Reflecting in remote:
Earlier I selected multiple commits and used allow empty when i didn't properrly know about it. Later on I did one commit and changed it and then pushed it. Similarly we can do it one by one.
name: Apoorv Gupta github_user_name: StephCurry07 discord_id: aphla.bet