-
Notifications
You must be signed in to change notification settings - Fork 18
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
YAML output isn't useful #70
Comments
Hello, Ross, this is Oleg, and I would like to work on the YAML issue. I am new to GitHub, so I don't know how to get assigned to an issue, and so I ask you if I could work on it. Thank you. |
Feel free to work on it Oleg, I haven't done anything on this. |
Thank you. But what about being assigned to it, I mean on the assignee menu? |
The maintainer can do that, but that isn't essential. |
Yes, not essential but done. Please let us know if you need any guidance. The developer docs should (hopefully) be relatively comprehensive. |
Hello, Ross. I have fixed the problem and I am trying to push, but I have encountered an issue when running the command git push: Can you please tell me why is this happening? |
You should create a fork of git-pw in your own account, and push to that. |
Fixes bug: getpatchwork#70 with incorrect output for 'Patches' property in .yaml format. Signed-off-by: Oleg Ananiev <[email protected]>
Thanks for the help. The pull request is submitted. |
For example:
The patches are not expressed in yaml in a way that is actually parsable.
The text was updated successfully, but these errors were encountered: