is:open is:issue assignee:@meOpen issues assigned to the current user (@me) is:closed is:pr author:contosoClosed pull requests created by@contoso is:pr sidebar in:commentsPull requests where "sidebar" is mentioned in the comments is:open is:issue label:bug -linked...
Contributing to Open Source: A Live Walkthrough from Beginning to End- This walkthrough of an open source contribution covers everything from picking a suitable project, working on an issue, to getting the PR merged in. "How to Contribute to Open Source Project" by Sarah Drasner- They are ...
Since this PR doesn't touch the codebase, I'll merge it without review. Some comments on CuDF's implementation of Arrow: We have to go down a different rabbithole to find the indexes and dictionary of a categorical variable than we do with pyarrow (not surprising). The index is not ...
Here, you learn about GitHub Actions and workflows for CI.You learn how to:Create a workflow from a template. Understand the GitHub Actions logs. Test against multiple targets. Separate build and test jobs. Save and access build artifacts. Automate labeling a PR on review....
Today I'm going to tell you in detail how to start participating in open source projects and help you complete your first PR on GitHub. Of course, in addition to the normal PR merging process, I am also going to introduce in detail how to solve relatively complex problems such as conflic...
7、Reviewing a PR Locally For more complicated PRs, if the author also didn't include any screenshot of the test they had run (see this example here,) it's better to check out the code locally and review it with the help of anIDE. ...
even if it’s so that you understand the backbone of the website and how it’s actually running. And those are really all the requirements you need to start GitHub hosting. If you check all three boxes, it’s time to move on to the next step, which is creating your new repository....
For example, GitHub already showed how many lines of code changes there are in a PR. There are tools to tell you what is a "big" function, a "large" file; how many "big" functions and "large" files you've got in your repo; their percentage; etc. ...
In your fork, create a branch off of main (git checkout -b mybranch). Name the branch so that it clearly communicates your intentions, such as "issue-123" or "githubhandle-issue". Make and commit your changes to your branch.
However, the major work of GitHub begins when users collaborate during projects. Teams are vital to the process because a group of people ultimately build many development projects, as opposed to coding individuals. Sometimes, such teams work in a single location, working asynchronously. This ...