public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: James Ed Randson <jimedrand@disroot.org>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Reksi Rizki Firdaus <jimedrand@gnuweeb.org>,
	"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>,
	Michael William Jonathan <moe@gnuweeb.org>
Subject: Re: Request to install Devin.ai Integration in GNUWeeb
Date: Sat, 2 Aug 2025 08:05:23 +0700	[thread overview]
Message-ID: <20250802080523.790ea9df@jimed-archie> (raw)
In-Reply-To: <CAFBCWQL5g7CXbQmA6x7LB9LkfY26VvQW6ra=8Z2svKV=sZ5OVQ@mail.gmail.com>

Pada Sat, 2 Aug 2025 07:49:02 +0700
Ammar Faizi <ammarfaizi2@gnuweeb.org> menulis:

> It's not read-only; the prompt page I get says:
> 
>   "Read and write access to code, discussions, issues, pull requests,
> and workflows"

Ah, I though it's read-only.

> I will allow the integration, both read and write, but only for
> specific repositories. Not "All repositories". Let me know which
> repository you want it to have access to.

Okay, I'm gonna activate it severe repo I'd choose

- GNUWeeb/waydroid (soon will be gwaydroid)
- GNUWeeb/gwanbox (continuation of Anbox under my pathces)
- GNUWeeb/gwproxy (for documentation only on deepwiki.com)
- GNUWeeb/jim-aur (for documentation on my AUR repo)
- GNUWeeb/anbox-modules (focused on "binder" docs)

That's it for the repo you need to give the access. Let me know when
it's connected (you can reply the mail wiht images or ping me at
Telegram for telling me it's done).

Regards

Jim


  reply	other threads:[~2025-08-02  1:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <688d543d887_10f107887267@lowworker-f496bdf97-cxkl5.mail>
2025-08-02  0:00 ` Request to install Devin.ai Integration in GNUWeeb Ammar Faizi
2025-08-02  0:07   ` James Ed Randson
2025-08-02  0:19     ` Ammar Faizi
2025-08-02  0:39       ` James Ed Randson
2025-08-02  0:49         ` Ammar Faizi
2025-08-02  1:05           ` James Ed Randson [this message]
2025-08-02  1:13             ` Ammar Faizi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250802080523.790ea9df@jimed-archie \
    --to=jimedrand@disroot.org \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=jimedrand@gnuweeb.org \
    --cc=moe@gnuweeb.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox