-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versions 0.2.0 -> 0.4.0 not committed? #7
Comments
Hi!
We are at version 0.0.2 (see pyproject.toml 😉)
Yes, you are right, thanks for pointing that out. The README.md shows, that all files should go into one directory for one issue. I filed #8 for that (will be fixed soon).
This could be, because I do not address the API correctly: I ignore pagination and therefore it could be possible, that API limits will be triggered. Pagination is on the TODO-list (see #5). I still need some time because I realized that downloading many projects takes a long time. I am currently working my way into asyncio / aiohttp to make the downloads faster (see #4). |
This is fixed now, see #8 |
Hello,
Could it be that versions 0.2.0 until 0.4.0 were not committed? In the README.md it mentions cli commands like "yt cp", "yt -q" and "yt gt", but these are not configured in the cli.py file as far as I can tell. Which also means that I cannot execute them.
There's other differences I noted, like the .md file of the issues which are not put in the folder of the issue but in the project folder. In itself nothing major, except that the .md does contain references to files/images that it expects to be in the same folder as the .md file.
I also have a difference in the projects it actually downloads vs the list it gives when I do "yt ls" (which in turn is also a more limited list compared to the hundreds of projects we actually have in our YouTrack).
Thanks in advance.
Kind regards,
Bram
The text was updated successfully, but these errors were encountered: