Skip to content
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

Patch testing script: Mantis > Github PR request maker #33

Open
luzpaz opened this issue Nov 2, 2015 · 3 comments
Open

Patch testing script: Mantis > Github PR request maker #33

luzpaz opened this issue Nov 2, 2015 · 3 comments

Comments

@luzpaz
Copy link

luzpaz commented Nov 2, 2015

In order to facilitate more efficient testing of patches for the Scribus community we suggest an automated script that will streamline sending a PR request to the repo to test the patch.
The script should:

  1. accept input of a Scribus MantisBT issue url (example url)
  2. grab the .patch file (not sure this is even possible)
  3. implement patch locally
  4. submit as a PR to scribusproject/scribus for testing
@luzpaz
Copy link
Author

luzpaz commented Nov 2, 2015

Posted question to MantisBT forums: http://fluffy.mantisbt.org/forums/viewtopic.php?f=2&t=23450&p=58307#p58307

@aoloe
Copy link
Contributor

aoloe commented Nov 2, 2015

i think it's easier to get the first tester to make a pull request to github after having applied the patch... and the other ones will profit from it...
the problem with patches coming from different sources is that they don't always cleanly apply at the first try...

@luzpaz
Copy link
Author

luzpaz commented Nov 28, 2015

A client side solution could be implemented by using the Mantis SOAP API or by direct access of the database (if attachments are stored in database) or by any client that sends HTTP requests and interprets the answers. A server side solution could be implemented in PHP using the internal Mantis API or by direct access of the database and the filesystem (if attachments are stored on disk)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants