Document how to vendor a repo

[hmpf]

No description provided.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.59%. Comparing base (5a6b8c1) to head (84a4991).
Report is 43 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #964      +/-   ##
==========================================
+ Coverage   81.93%   82.59%   +0.65%     
==========================================
  Files         132      129       -3     
  Lines        4861     4808      -53     
==========================================
- Hits         3983     3971      -12     
+ Misses        878      837      -41     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[podliashanyk]

Bunch of typos, another bunch of formatting issues, see below.

A suggestion for better readability: uppercase the GIVING and RECEIVING.
I would also suggest to replace the "giving-receiving" pair with f.e. "in-out" or "origin-target" for a better clarity IMO

[hmpf]

A suggestion for better readability: uppercase the GIVING and RECEIVING. I would also suggest to replace the "giving-receiving" pair with f.e. "in-out" or "origin-target" for a better clarity IMO

I went with ORIGIN and TARGET.

[lunkwill42]

It is definitely good to have a how-to for this, but even though this operation has been done once for argus and argus-htmx-frontend, it strikes me as a strange thing to have generic documentation for in Argus - it's not exactly documentation of Argus itself, or even some maintenance operation we can expect to be doing regularly for Argus.

I feel like this would more appropriately belong in some external knowledge base or wiki for our team.

[hmpf]

I feel like this would more appropriately belong in some external knowledge base or wiki for our team.

As long as it is public and I can find it when I need it. This is useful for more than our team.

[podliashanyk]

See a comment below about heading levels

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[lunkwill42]

Nice work. Still not sure this really belongs in the Argus docs, though. Maybe we need our own tech blog? ;)