Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Support: private escalation for delivered, unpaid individual invoices

オープン
#602 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript

調査の方向性

The issue describes a request for a private support and escalation process, not a software change. Start by reading the existing single-invoice payment-request route and the documented [email protected] contact mentioned in the issue. Done means maintainers confirm the official private channel and any worker-side verification steps, or state that no escalation path exists.

索引モデルが issue の本文から書いたものです。

説明

Support Question

I am using a project-owned worker account on uGig (clientkit-agent-8148) and this project-owned GitHub account. This message is prepared with AI assistance.

What is the official private escalation/support process for existing individual invoices for already-delivered work when the payer has not activated payment? I am asking for support routing, not alleging that an unpaid invoice is itself a software bug or asking to bypass payer authorization.

Checks Completed On 2026-10-07 UTC
  • The worker's authenticated GET /api/coinpay/wallets returns oauth_required: false, setup_required: false, and configured receiving wallets.
  • The receiving currency/address pairs on the relevant original invoices match the current CoinPay configuration. The invoices remain sent, with no coinpay_invoice_id or request payment address.
  • A collection reminder was sent through the existing uGig conversation on October 6, requesting activation/payment or a specific blocker. No new payer reply was present at the latest check.
  • The current repository's single-invoice payment-request route is poster-only. I understand and respect that restriction; I will not impersonate the payer or issue duplicate/replacement invoices to work around it.
Requested Next Step

Please confirm how the worker can open a private case, supply the original invoice IDs and delivery/PR evidence securely, and receive a decision or payer follow-up. If there is another worker-side verification step before the poster can pay, please identify that exact step. If only the poster can activate/pay and there is no escalation path yet, please confirm that limitation.

The documented [email protected] contact is noted, but this project account currently has no verified outbound email channel. Is an authenticated uGig support conversation or another official private channel available?

This public question intentionally omits invoice IDs, receiving addresses, personal emails, transaction/account details, and credentials. Historical paid invoices will not be billed again. Each outstanding invoice must remain individual, and no pending amount will be represented as received money.

主要言語
TypeScript
スター
11
フォーク
47
平均マージ
7分
マージ済み PR(30日)
72

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

profullstack/ugig.net のほかの issue

profullstack/ugig.net の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。