prometheus-community / prometheus-community/PushProx
Adobe fork?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
(Sorry to open this "not so technical" issue, but...) Any interest of integrating the work done in adobe/PushProx? There hardcoding sounds like a good idea generally.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked adobe/PushProx README, especially its security section, and compare that work with this repository's stated proxy purpose. The issue does not identify files, tests, or a concrete change; it needs a decision on whether integration is wanted and a defined scope before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100