latexcv VS starter-workflows

View on GitHub

I generally avoid sending Word documents. IMO scanning PDFs is nowadays good enough to deal with LaTeX-generated PDFs. And when it comes to the templates... Personally I use LaTeX generated. Some time ago I was using LibreOffice but updating it was not pleasant. I wanted to have more fancy CV and store the source in GIT. I have chosen Sidebar Left from this repo: https://github.com/jankapunkt/latexcv and I am generally satisfied, but I also respect the above approach.

And for all resumes in https://github.com/jankapunkt/latexcv , I think they're not appropriate for CS resumes as they're too fancy

IMHO - Look at a different resume style nothing is jumping out at me and it's the style not the person. This is an older style very bland. There are lots of creative styles out there, you want to find what is most valuable about you and make that pop everything else is details. Example - https://github.com/jankapunkt/latexcv - this is just a few examples after a quick Google, I personally refuse to put my picture on there but a resume can show personality use it to your advantage.

Ja ga koristim za fakture, ali imas jako puno primera za CV u LaTeX-u (https://github.com/jankapunkt/latexcv)

GitHub, as one of the leading web-based Git repository hosting service, provides a powerful suite of CI/CD tools in the form of GitHub Actions. These are directly integrated into the platform which empowers developers to increase the speed, efficiency and reliability of delivering products. In this brief article, we will take a look at what CI/CD is, why we should use it, as well as some of its applications in my projects.

GitHub Actions is a modern CI/CD tool integrated natively on GitHub. Itenables the rapid automation of build, test, deployment, and other custom workflows on GitHub with no need for external tools.

GitHub Actions is GitHub's CI/CD solution. You can use it to run automated tasks each time you change your code. Although the platform lacks a built-in Kubernetes integration, third-party plugins such as Azure's Deploy to Kubernetes Cluster action can automate deployments and manage different rollout strategies.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).