![]() ![]() ![]() How to Keep Your Feature Branch Up-to-date The maintainer can always initiate a re-run of a CI job on the failed platform if need be. Unless you see the failure is related to your PR, please ignore it and consider that all tests have succeeded. You can go to Azure CI following the failing link and check what has failed. We are constantly trying to make those less error-prone, but we can’t make them too loose either, otherwise the test would be ineffective. Most of the time it’s normal, and there is nothing to worry about. The tests run on various platforms and on both pip and conda virtual environments, so we have all bases covered.ĭo note that since our test suite contains many non-deterministic tests, at times you will notice that one of the checks on a single platform will fail. Once your PR was submitted, you will see on github that we have various tests running on CI servers that will validate your PR. If you work on several unrelated PRs, make different directories for each one, ideally using the same directory name as the branch name, to simplify things. If for any reason it’s not working, go to (replace new-feature-branch with the real branch name, and click in the right upper corner. Usually, if you go to github will notice that you committed to a new branch and will offer you to make a PR, so you don’t need to figure out how to do it. Go to github and make a new Pull Request: The following url shows all three, in the order they have been mentioned: If you’d like to contribute to other fastai-project repositories, just replace fastai with that other repository name in the instructions below.įor the purpose of these examples, we will clone into a folder fastai-fork, to differentiate from fastai which you most likely already checked out to install it.Īlso don’t get confused between the fastai github username, the fastai repository, and the fastai module directory, where the python code resides. The easiest way to follow this guide is to copy-n-paste the whole section into a file, replace USERNAME with your real username and then follow the steps.Īll the examples in this guide are written for working with the fastai1 repository. The following instructions use USERNAME as a github username placeholder. If you already know how to make PRs, you only need to read: the “Step 3” and “Step 5” sections, since they are unique requirements for the fastai project. While this guide is mostly suitable for creating PRs for any github project, it includes several steps specific to the fastai project repositories, which currently are: This document has a variety of useful recipes that might be of help in your work. Chances are that you may need to know some git when using fastai - for example if you want to contribute to the project, or you want to undo some change in your code tree.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |