Changes between Version 1 and Version 2 of SummerOfCode/bump

Timestamp:

Aug 16, 2019, 5:17:55 AM (5 years ago)

Author:

satraul (Satryaji Aulia)

Comment:

--

SummerOfCode/bump

@@ -20 +20 @@
 == What hasn't been done
 
-**@version/--livecheck argument**
+**@version argument**
 
 Ideally, the port maintainer doesn't have to manually update the Portfile's version first before running `port bump`, instead with simply running `port bump @version`, MacPorts will change the version by itself.
@@ -26 +26 @@
 
 This idea can be discussed further with the people from the PR or the Xcode project.
+
+**--livecheck argument**
+
+As the extension of the @version argument, `port livecheck` should be integrated somehow so MacPorts will bump to the latest version from livecheck.
+
+** Extended goals: batch bump, dry run, and Git actions
+
+We could also implement a batch bump function that bumps a lot of ports at once. Doing this is dangerous unsupervised, so ideally it should also build and test the Port. Or it could run semi-automated with human supervision.
+To further extend the functionality, we could take inspiration from brew’s bump-formula-pr which can do a dry run (only printing what would be the changes) or automatically take Git actions, such as commits or opening a PR. Just like the batch functionality, the updated Port should first be built and test before being commit. To avoid over-automating, we could tell the user the link to open a PR instead of doing it for them. For example:
+{{{
+$ port bump
+---> Bumping checksums for libpng
+Version successfully updated. Suggested commit message:
+    chromedriver: update to 6.6.3
+Review your changes and open a Pull Request at:
+    https://github.com/macports/macports-ports/compare/master...user:master
+}}}