From ab19aab187ec6792e68cc095398f48438edb9a75 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 16 Oct 2023 10:20:26 +0000 Subject: [PATCH] Update docs --- atom.xml | 2 +- rss.xml | 2 +- tag/blog-atom.xml | 2 +- tag/blog-rss.xml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/atom.xml b/atom.xml index 4cd8d5b..b50a8ff 100644 --- a/atom.xml +++ b/atom.xml @@ -1,5 +1,5 @@ - 40Ants Mon, 09 Oct 2023 10:21:51 +0000 Alexander Artemenko Pushing your pulls faster! 2019-04-30 23:00 2019-04-30 23:00 Alexander Artemenko 40ants.com <div class="document"><p>Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.</p> + 40Ants Mon, 16 Oct 2023 10:20:14 +0000 Alexander Artemenko Pushing your pulls faster! 2019-04-30 23:00 2019-04-30 23:00 Alexander Artemenko 40ants.com <div class="document"><p>Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.</p> <p>I believe that tickets and pulls creators create them to improve their open source projects of interest. In order to do that, tickets must become pulls. The pulls in turn should merge in a timely manner. The faster this process will be, the quicker open source projects will be developed.</p> <p>Yet, communication around a ticket or a pull often gets less intense and can be lost on GitHub. This situation can arise for a number of reasons. As a rule, some participant misses a GitHub email notification about a comment, and the issue emerges. The end result stays the same despite various reasons — a ticket is lost. At times, it may take years for the ticket to be discovered.</p> <p>For that matter, there are special pages on GitHub, of course. E. g. see web pages with pull lists on <a class="reference" href="https://github.com/pulls"><span>https://github.com/pulls</span></a> and web pages with ticket lists on <a class="reference" href="https://github.com/issues"><span>https://github.com/issues</span></a>. Yet, these lists are not user-friendly, as they don’t give you a slightest idea about which ticket requires your reaction and which does not. That’s what I’m going to fix.</p> diff --git a/rss.xml b/rss.xml index 2c15f58..14a4fb4 100644 --- a/rss.xml +++ b/rss.xml @@ -1,5 +1,5 @@ - 40Ants 40ants.com en-us Mon, 09 Oct 2023 10:21:51 +0000 Pushing your pulls faster! 40ants.com/posts/Pushing-your-pulls-faster.html 2019-04-30 23:00 Alexander Artemenko 40ants.com/posts/Pushing-your-pulls-faster.html

Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.

+ 40Ants 40ants.com en-us Mon, 16 Oct 2023 10:20:14 +0000 Pushing your pulls faster! 40ants.com/posts/Pushing-your-pulls-faster.html 2019-04-30 23:00 Alexander Artemenko 40ants.com/posts/Pushing-your-pulls-faster.html

Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.

I believe that tickets and pulls creators create them to improve their open source projects of interest. In order to do that, tickets must become pulls. The pulls in turn should merge in a timely manner. The faster this process will be, the quicker open source projects will be developed.

Yet, communication around a ticket or a pull often gets less intense and can be lost on GitHub. This situation can arise for a number of reasons. As a rule, some participant misses a GitHub email notification about a comment, and the issue emerges. The end result stays the same despite various reasons — a ticket is lost. At times, it may take years for the ticket to be discovered.

For that matter, there are special pages on GitHub, of course. E. g. see web pages with pull lists on https://github.com/pulls and web pages with ticket lists on https://github.com/issues. Yet, these lists are not user-friendly, as they don’t give you a slightest idea about which ticket requires your reaction and which does not. That’s what I’m going to fix.

diff --git a/tag/blog-atom.xml b/tag/blog-atom.xml index 2043bb0..22e901d 100644 --- a/tag/blog-atom.xml +++ b/tag/blog-atom.xml @@ -1,2 +1,2 @@ - 40Ants Mon, 09 Oct 2023 10:21:51 +0000 Alexander Artemenko \ No newline at end of file + 40Ants Mon, 16 Oct 2023 10:20:14 +0000 Alexander Artemenko \ No newline at end of file diff --git a/tag/blog-rss.xml b/tag/blog-rss.xml index 9bb702c..1a0c31d 100644 --- a/tag/blog-rss.xml +++ b/tag/blog-rss.xml @@ -1,2 +1,2 @@ - 40Ants 40ants.com en-us Mon, 09 Oct 2023 10:21:51 +0000 \ No newline at end of file + 40Ants 40ants.com en-us Mon, 16 Oct 2023 10:20:14 +0000 \ No newline at end of file