chore: add Jenkins documentation to Devops

[goobric]

Closes #1931

Fixes Issue

Closes #1931

Changes proposed

Added Jenkins documentation to the Devops category

Screenshots

Note to reviewers

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
linkshub	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 13, 2023 7:51am

[github-actions]

Thank you, goobric, for creating this pull request and contributing to LinksHub! 💗

The maintainers will review this Pull Request and provide feedback as soon as possible! 😇
We appreciate your patience and contribution, Keep up the great work! 😀

[CBID2]

Well done @goobric. Just needs improvement

[Anmol-Baranwal]

@goobric
You need to add it here: database\data.ts

As you can see it's not visible.

[Anmol-Baranwal]

@goobric
Why did you delete the head repo?

[goobric]

hi @Anmol-Baranwal
I responded to this message yesterday at about 14:10 UTC, using the github app on my mobile/cell phone; yet my response isn't listed!
I updated the data.ts file with the 'jenkins' information:

• saved the file locally on my cloned repo
• added the file
• committed the file
• pushed the file
  received an error message about 'fast-forward' use 'pull' command from forked repo
  tried to 'pull' my forked repo; received another error!
  So I thought, "maybe it's better to start again" (clearly this was the wrong approach); so I deleted my locally cloned repo; deleted the forked repo from my github account.
• I forked the original repo to my gh account;
• cloned the repo to my local computer
• created a new branch
• added details about 'jenkins' to index, data.ts, CategoryDescription.ts, added jenkins.json in the devops directory
• saved the files locally
• added the files to the stage
• commited the files
• pushed the files to my forked repo
  Everything pushed successfully to my forked repo
• yet, on my repo; there was no option to "Compare & PR" !
  What did I do wrong? please explain to me what I should have done, to have a successful PR?

[goobric]

@Anmol-Baranwal what do I do now?
Do I start the process again from the beginning? I am confused!

[Anmol-Baranwal]

@goobric Comment on this PR: #1976

[Anmol-Baranwal]

I mistakenly created a PR, so the PR will be merged as a co-authored commit.

If you want to only do it urself, then you can create a fresh PR.

For now: it will be similar to this, we both will be assigned to the PR.

[goobric]

@Anmol-Baranwal that's great :-)
thanks for co-authoring, I have never co-authored a PR before!
This should be a common option on github (probably is already) I would like to co-author on more PRs; but I don't know how.
I am a big advocate of pair-programming and problem solving.
Thanks for creating the PR and merging it.
Have a wonderful weekend.

[Anmol-Baranwal]

It hasn't been merged, you need to comment there in order for me to assign the PR to you.

Then we can go forward.

[goobric]

@Anmol-Baranwal
I am so sorry to ask such a stupid question, but what do I need to say in the comment for the PR to be assigned?
Do I just say, "Please assign this PR me"

[Anmol-Baranwal]

@goobric
Comment anything. GitHub works in a way, that those who have raised or commented can be assigned.

So, it is not showing your option for assignee.

As you can see, your name is not available for assignee.

[Anmol-Baranwal]

See once someone comments.

His name is available.