Skip to content

Commit

Permalink
Update docs
Browse files Browse the repository at this point in the history
  • Loading branch information
actions-user committed Mar 20, 2024
1 parent 0d7ad6c commit 76bd6ef
Show file tree
Hide file tree
Showing 5 changed files with 106 additions and 79 deletions.
2 changes: 1 addition & 1 deletion atom.xml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom"> <title>40Ants</title> <link href="40ants.com"/> <link type="application/atom+xml" rel="self" href="40ants.com/atom.xml"/> <updated>Mon, 18 Mar 2024 16:31:55 +0000</updated> <author> <name>Alexander Artemenko</name> </author> <entry> <link type="text/html" rel="alternate" href="40ants.com/posts/Pushing-your-pulls-faster.html"/> <title>Pushing your pulls faster!</title> <published>2019-04-30 23:00</published> <updated>2019-04-30 23:00</updated> <author> <name>Alexander Artemenko</name> <uri>40ants.com</uri> </author> <content type="html">&lt;div class=&quot;document&quot;&gt;&lt;p&gt;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.&lt;/p&gt;
<feed xmlns="http://www.w3.org/2005/Atom"> <title>40Ants</title> <link href="40ants.com"/> <link type="application/atom+xml" rel="self" href="40ants.com/atom.xml"/> <updated>Wed, 20 Mar 2024 13:48:00 +0000</updated> <author> <name>Alexander Artemenko</name> </author> <entry> <link type="text/html" rel="alternate" href="40ants.com/posts/Pushing-your-pulls-faster.html"/> <title>Pushing your pulls faster!</title> <published>2019-04-30 23:00</published> <updated>2019-04-30 23:00</updated> <author> <name>Alexander Artemenko</name> <uri>40ants.com</uri> </author> <content type="html">&lt;div class=&quot;document&quot;&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;For that matter, there are special pages on GitHub, of course. E. g. see web pages with pull lists on &lt;a class=&quot;reference&quot; href=&quot;https://github.com/pulls&quot;&gt;&lt;span&gt;https://github.com/pulls&lt;/span&gt;&lt;/a&gt; and web pages with ticket lists on &lt;a class=&quot;reference&quot; href=&quot;https://github.com/issues&quot;&gt;&lt;span&gt;https://github.com/issues&lt;/span&gt;&lt;/a&gt;. 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.&lt;/p&gt;
Expand Down
Loading

0 comments on commit 76bd6ef

Please sign in to comment.