Mininote pro 5.3 professional#
If that doesn't work, consider switching to contribute to another repository. If you can't get a maintainer for a repository to respond to your Issues, or give feedback on reviews, you should try and reach out on Slack. Please use Open Source Slack to help with communication. Don't struggle on your own and get stuck, or miss the due date. Leave that for the very end, when your fully reviewed and corrected pull request will (hopefully) get merged by the repository maintainer.Īt every stage of your work, make sure you ask for help, and get feedback from others in the community by asking questions. Don't worry if you make mistakes, or need to overwrite/undo something just add more commits to fix the problems. On your new branch, you can make as many commits as you need to. If the issue you filed was #5, create a branch named issue-5.
Mininote pro 5.3 code#
You must create a new branch before you commit any code or submit a pull request. Once your issue is filed, begin your fix by forking the appropriate repository and creating a new branch. Don't duplicate someone else's work, or get in the way of another contributor. In both cases, before you file any new issues in a repository, take a look at the other issues that are already filed, and any pull requests that have been made. You'll need to convince the repository's owner that your idea is worth doing, and give enough detail about your change for them to think it necessary. You can use the list of suggested features from Lab 2 or suggest your own.
The second issue should be to add a new feature to a second repository. Respect the existing coding style of the author vs. This does not include making coding style changes. You're looking for a way to help make the app and/or code better than it currently is. Read the code and see if there are any problems you notice with the way it's been written. Try running the code, and see if you can find any bugs. The first issue should be to fix or improve something in the repository's existing code.
Mininote pro 5.3 how to#
See this article on GitHub for more details on how to file an issue. You are asked to file 2 separate Issues, each in a different repository from the Lab 2 Submissions list. Watching your repository is important so that when other people start filing bugs below, you get notifications and can respond. By default, GitHub will not set a watch on repositories you create, and you won't see email notifications when people file issues or send pull requests. You will also have the chance to work on multiple issues across different repositories, and learn more about what it's like to work with code you didn't write, and with other collaborators on the same project.īefore you do anything else, begin by Watching your repository from Lab 2.
0 kommentar(er)
