One of the advantages of organizations here is reducing the bus factor
for operational matters.  If a group member is using their account
credentials to e.g. run CI/CD, and that group member is for any reason
unavailable, what's the plan for the rest of the group to make needed
changes?  With an org-specific credential which members can access,
other users can step in to mitigate problems.  If everyone is using
their own creds for API access, that collaboration gets harder.  

To be clear: I'm not an expert in SourceHut architecture.  I'm asking 
these questions because I don't know the answer, not out of some 
Socratic drive to make a point in the mind of the reader.

Thanks,
khm

Hello,

I am trying to make a user CSS file to remove the syntax highlighting
from the web view of files on sr.ht.  Mostly, this is sufficient:

.highlight * { 
  color: inherit !important;
  font-weight: inherit !important;
}

However, some elements (specifically .cp and .nl) already have
!important tags in the main.min.css as delivered by the server.  These 
override *other* CSS directives delivered by the server inline with 
the HTML.

removes GNUish %z thing, nails timezones to UTC
---
 commit-tree | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/commit-tree b/commit-tree
index bde1ed9..35a03f9 100755
--- a/commit-tree
+++ b/commit-tree
@@ -33,9 +33,8 @@ then
 fi
 GIT_COMMITTER_NAME=${GIT_COMMITTER_NAME:-$GIT_AUTHOR_NAME}
 GIT_COMMITTER_EMAIL=${GIT_COMMITTER_EMAIL:-$GIT_AUTHOR_EMAIL}
-# XXX: GNUism
[message trimmed]