-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fix for "ValueError: Attempted relative import in non-package" - In windows system #43
Conversation
@fazalsulaiman thanks for creating this Pull Request and help improve Plone! To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass. Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:
With this simple comment all the jobs will be started automatically. Happy hacking! |
@mauritsvanrees : Please review the change and merge the MR |
@jenkins-plone-org please run jobs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to make sense, but I cannot try it, so I prefer a second opinion from @jensens.
Feel free to merge in a day when there is no reaction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - even I also did not try this. But if it works for @fazalsulaiman it should be fine.
@jenkins-plone-org please run jobs |
I started the Jenkins jobs an hour ago, then you did the same half an hour later, and then a minute later you merged... Anyway, I checked the jobs that I started and they were all green, so it's okay. But in my part of the world it is hot enough already: we don't need extra heat generated by a server running those jobs. ;-) But thanks for working on Windows issues! Great to have more people who care about that! |
@mauritsvanrees While the plone contributing process is much more streamlined than most others I know, isn't it possible to restrict merging to successfully tested branches? This would take away some burden from new contributors to go through a pretty long mental checklist. |
Sure, this is possible, but we need to add the protected branches for every single repository in Plone, that's quite annoying. I added master branch protection for this repository now. |
This should be possible via API, but at 35 ° C it is preferable to go to beach and keep the status quo 😉 |
Thank you @mauritsvanrees for the details and I will follow that |
No description provided.