Browse Source

added to documentation on using Gitea

master
apoc 1 year ago
parent
commit
8e8852da38
2 changed files with 3 additions and 4 deletions
  1. 2
    2
      docs/Series/2. git/2.5 Gitea/2.5.1 Access
  2. 1
    2
      docs/issue-tracker.org

+ 2
- 2
docs/Series/2. git/2.5 Gitea/2.5.1 Access View File

@@ -14,6 +14,6 @@ So, a repository/a project, is a box in which code lives.
How to make changes?
In order to make changes on files within this repository you can either follow the workflow of: fork->change->create pull request;

or you can become a collaborator, in order for you to become a collaborator I need to add your (teknik.io) account to the list of collaborators, BUT in order to do that I've to invent a way for you to contact me...
or you can become a collaborator, in order for you to become a collaborator I need to add your (teknik.io) account to the list of collaborators, for which you need to

To be continued.
email me about it:

+ 1
- 2
docs/issue-tracker.org View File

@@ -27,9 +27,8 @@
https://stockholm.craigslist.org/lss/d/koreanska-lektioner-korean-lessons/7122935441.html?lang=en&cc=us

And create a simple (very simple (seriously make it as simple as possible)) HTML page like that. Call it view.html
Add the view.html you made to the pages/advertisement/ in this repository and do so by creating a pull request. For more information read Contributing.md

In short, click the "fork" button above to fork this repository to your git(ea/hub) account, edit the file, then from your fork of the repository click "create full request".
When done paste the HTML into a new "view.html" file within this project pages/advertisement directory.

**** Solution


Loading…
Cancel
Save