Commit Graph

79 Commits

Author SHA1 Message Date
George
55a2685683
Unify jsonresume and RenderCV CVs solutions (#3462)
Fixes #2787 as an alternative to #2969. It was getting too cumbersome to
have 2 different data sources for CV and also a lot of different layout
files, so I decided to unify them all.
Main changes:
- synchronized the information inside RenderCV (`_data/cv.yml`) and
JSONResume (`assets/json/resume.json`)
- unified layout files for CV information
- added the option to set the "data source" in the CV page

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
2026-01-23 12:36:14 -03:00
George
a66d975b68
Refactor docker-slim workflow configuration
Updated docker-slim GitHub Action version.
2025-11-21 19:19:08 -03:00
Dominik Fuchß
1f349ffda2
Adapt mechanism for citiation count (#3177)
## Summary

This PR introduces an automated mechanism to update the citation count
for authors' publications.

- Inspired by @BernardoCama’s suggestion in #3150.
- Resolves #3150.

## Key Changes

- Adds an action to update publication citation counts.
    - Note: This action creates a commit on the main branch.
- To trigger further GitHub Actions workflows from this commit, a
Personal Access Token (PAT) must be used (the default GitHub Actions
token cannot trigger subsequent workflows).
- Adds and manages citation data in `_data/citations.yml`.
- Adds and adapts `bin/update_scholar_citations.py` to handle citation
updates.

## Usage Examples
### Timeout
<img width="758" height="415" alt="image"
src="https://github.com/user-attachments/assets/0a330d35-b386-4670-8668-62701f2dc68b"
/>

### Success

<img width="1684" height="857" alt="image"
src="https://github.com/user-attachments/assets/44aa0558-e02a-4f00-b8cb-9e0ce16dd53c"
/>
2025-11-16 22:17:17 -03:00
dependabot[bot]
332fbeb204
Bump lycheeverse/lychee-action from 1.9.0 to 2.0.2 in /.github/workflows (#3285)
Bumps
[lycheeverse/lychee-action](https://github.com/lycheeverse/lychee-action)
from 1.9.0 to 2.0.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/lycheeverse/lychee-action/releases">lycheeverse/lychee-action's
releases</a>.</em></p>
<blockquote>
<h2>Version 2.0.2</h2>
<h2>What's Changed</h2>
<ul>
<li>Fix a typos by <a
href="https://github.com/szepeviktor"><code>@​szepeviktor</code></a> in
<a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/257">lycheeverse/lychee-action#257</a></li>
<li>Document and use correct permissions in the GitHub workflows by <a
href="https://github.com/dscho"><code>@​dscho</code></a> in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/258">lycheeverse/lychee-action#258</a></li>
<li>Add security policy by <a
href="https://github.com/mondeja"><code>@​mondeja</code></a> in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/259">lycheeverse/lychee-action#259</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a
href="https://github.com/szepeviktor"><code>@​szepeviktor</code></a>
made their first contribution in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/257">lycheeverse/lychee-action#257</a></li>
<li><a href="https://github.com/mondeja"><code>@​mondeja</code></a> made
their first contribution in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/259">lycheeverse/lychee-action#259</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/lycheeverse/lychee-action/compare/v2...v2.0.2">https://github.com/lycheeverse/lychee-action/compare/v2...v2.0.2</a></p>
<h2>Version 2.0.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Don't remove the lychee config file by <a
href="https://github.com/dmathieu"><code>@​dmathieu</code></a> in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/255">lycheeverse/lychee-action#255</a></li>
<li>Bump lycheeverse/lychee-action from 1 to 2 by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/252">lycheeverse/lychee-action#252</a></li>
<li>Fix variable name in docs by <a
href="https://github.com/kdeldycke"><code>@​kdeldycke</code></a> in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/253">lycheeverse/lychee-action#253</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/dmathieu"><code>@​dmathieu</code></a>
made their first contribution in <a
href="https://redirect.github.com/lycheeverse/lychee-action/pull/255">lycheeverse/lychee-action#255</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/lycheeverse/lychee-action/compare/v2...v2.0.1">https://github.com/lycheeverse/lychee-action/compare/v2...v2.0.1</a></p>
<h2>Version 2.0.0</h2>
<h2>Breaking Changes</h2>
<p><strong>Note:</strong> This release improves the action's robustness
by changing default behaviors. Changes are only required if you want to
opt out of the new failure conditions. Most users won't need to modify
their existing configurations.</p>
<h3>Fail pipeline on error by default</h3>
<p>We've changed the default behavior: pipelines will now fail on broken
links automatically. This addresses user feedback that not failing on
broken links was unexpected (see [issue <a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/71">#71</a>](<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/71">lycheeverse/lychee-action#71</a>)).</p>
<p><strong>What you need to do:</strong></p>
<ul>
<li>Update to version 2 of this action to apply this change.</li>
<li>Users of the <code>lychee-action@master</code> branch don't need to
make any changes, as <code>fail: true</code> has been the default there
for a while.</li>
<li>If you prefer the old behavior, explicitly set <code>fail</code> to
<code>false</code> when updating:</li>
</ul>
<pre lang="yaml"><code>- name: Link Checker
  id: lychee
  uses: lycheeverse/lychee-action@v2
  with:
    fail: false  # Don't fail action on broken links
</code></pre>
<h3>Fail pipeline if no links were found</h3>
<p>Similar to the above change, we now fail the pipeline if no links are
found during a run. This helps warn users about potential configuration
issues.</p>
<p><strong>What you need to do:</strong></p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="7cd0af4c74"><code>7cd0af4</code></a>
Merge commit from fork</li>
<li><a
href="8ad54d3568"><code>8ad54d3</code></a>
fix link</li>
<li><a
href="762333c189"><code>762333c</code></a>
Create SECURITY.md (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/259">#259</a>)</li>
<li><a
href="71a38a3bd7"><code>71a38a3</code></a>
Document and use correct permissions in the GitHub workflows (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/258">#258</a>)</li>
<li><a
href="f141760066"><code>f141760</code></a>
Fix a typos (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/257">#257</a>)</li>
<li><a
href="2bb232618b"><code>2bb2326</code></a>
don't remove the lychee config file (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/255">#255</a>)</li>
<li><a
href="731bf1a2af"><code>731bf1a</code></a>
Fix variable name (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/253">#253</a>)</li>
<li><a
href="e360f3c891"><code>e360f3c</code></a>
Bump lycheeverse/lychee-action from 1 to 2 (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/252">#252</a>)</li>
<li><a
href="f87f0a6299"><code>f87f0a6</code></a>
Update version to <code>lycheeverse/lychee-action@v2</code> in docs</li>
<li><a
href="7da8ec1fc4"><code>7da8ec1</code></a>
Test latest lychee version tag (<a
href="https://redirect.github.com/lycheeverse/lychee-action/issues/236">#236</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/lycheeverse/lychee-action/compare/v1.9.0...v2.0.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lycheeverse/lychee-action&package-manager=github_actions&previous-version=1.9.0&new-version=2.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/alshedivat/al-folio/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-11-07 11:38:56 -08:00
George
58f4e02ab0
Changed order of params for gh-md-toc 2025-04-14 17:09:00 -03:00
George
78fdace28a
Update update-tocs.yml 2025-04-14 17:06:46 -03:00
George
c5bdfebd5b
Fixed tocs (#3133)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2025-04-14 17:02:59 -03:00
George
e4d5b06dbb
Using fork of gh-md-toc 2025-04-14 16:48:15 -03:00
George
91a2b63c80
Created GitHub action to update TOCs (#3132)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2025-04-14 15:39:55 -03:00
George
301132d2fd
Changed broken-links action to only run on main repo (#3118)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2025-04-09 11:41:26 -03:00
George
351dcb985e
Fixed liquid variables in some js files (#3117)
Fixes #3095

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
2025-04-09 11:36:16 -03:00
George
6625f2395a
Digital Bookshelf V2 (#2866)
Since I was annoyed at not being able to use
[jekyll-archives](https://github.com/jekyll/jekyll-archives) to create
an archive for the books, I decided to implement myself the
[jekyll-archives-v2](https://github.com/george-gca/jekyll-archives-v2)
that doesn't have this limitation.

Closes #923.

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
2025-02-28 13:57:36 -03:00
George
e3f029dcd1
Added sass changes to trigger deploy action 2025-02-09 12:21:55 -03:00
George
3795438a75
Updated dependencies (#2925)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-12-29 23:08:39 -03:00
George
e9916adb95
Create codeql.yml 2024-12-29 22:24:59 -03:00
Jiaqi Li
ec7d7c34e8
explicitly install imagemagick to support ubuntu-latest (>=24.04) in Github actions (#2906)
Install `imagemagick` within `Install and Build 🔧` step of Github
actions

Relevant issue: 
[#2902](https://github.com/alshedivat/al-folio/issues/2902) `convert`
Command Not Found on Ubuntu 24.04

Reason: 
`ubuntu-latest` in Github actions is pointed to `ubuntu-24.04` now, in
which `imagemagick` is no longer pre-installed. See
[this](https://github.com/actions/runner-images/issues/10772).

Modified files (actions) recommended by @george-gca 
```
- .github/workflows/deploy.yml
- .github/workflows/broken-links-site.yml
- .github/workflows/axe.yml
```
2024-12-19 17:55:36 -03:00
Isaac Fernandes
b37758a55c
Add .lycheeignore file with linkedin to stop error on workflow Linkcheck (#2868)
Add a .lycheeignore file with LinkedIn to stop the error in the workflow
Link Checker due to response 999, and update to the new version
lycheeverse/lychee-action@v2.1.0.
2024-12-02 16:37:42 -03:00
George
de2b3b87ae
Renamed all references to master branch to main (#2793)
Finishes #2086

Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-10-21 21:54:16 -03:00
George
6053d3f768
Added setup-python step to build (#2792)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-10-21 21:38:26 -03:00
George
6632074098
Update schedule-posts.txt 2024-09-09 14:58:05 -03:00
M. Umar Shahbaz
d50cdf6b8a
Schedule Posts Workflow (#2672)
Updated ```CUSTOMIZE.md``` to include information regarding the
```scheduler.yml``` action
2024-09-09 14:36:44 -03:00
George
6c6932f1b1
Removed inexistent input from lighthouse-badger.yml 2024-08-28 10:54:06 -03:00
M. Umar Shahbaz
fbad5083ae
Added gh-pages Formatter (#2649)
# Added prettier-hmtl.yml
## GitHub Workflow

## Purpose
The GitHub Workflow formats the html files on gh-pages. The html files
generated are always on a single line. This makes scaling programs a lot
more difficult. By formatting the HTML files, al-folio can now be used
to generate code which can then be modified to allow for using back-end.

## Errors found
I want to let you know that when I was using prettier for this, it kept
crashing and after some debugging I found out that al-folio was
generating an invalid tag ```</source>```. ```<source>``` is a
self-closing tag and doesn't have a separate closing tag.
Error: ```<source src="URL" type="type"></source>```
Correct: ```<source src="URL" type="type">```

## Workflow Description
1. The workflow starts by checking out the gh-pages branch.
2. Then it finds all ```</source>``` tags in all html files and deletes
them.
3. It Installs NodeJS and then Prettier. To make sure the code was
executed properly, the workflow checks if prettier is present.
4. Then the workflow runs prettier on all html files present in gh-pages
5. It ends by committing the changes and pushing them to the gh-pages
directory

# Example:
> Before
>
![image](https://github.com/user-attachments/assets/8f0f993a-1b18-4edf-9d62-2fe503af272a)

> After
>
![image](https://github.com/user-attachments/assets/0714a6c8-0b37-4aee-a4f0-4ce0a7a663a1)
2024-08-23 13:12:34 -03:00
Salman Faroz
e7da32f0e4
Lighthouse Badger token as secret (#2589)
In the
[FAQ](https://github.com/alshedivat/al-folio/blob/master/FAQ.md#my-webpage-works-locally-but-after-deploying-it-is-not-displayed-correctly-css-and-js-are-not-loaded-properly-how-do-i-fix-that),
it is mentioned to "add it as a secret". However, the Lighthouse Badger
documentation specifies using an environment variable. I've updated this
to use secrets instead, as it is more secure and appropriate for using a
Personal Access Token (PAT).

#### Personal Access Token (fine-grained) Permissions:
- **contents**: access: read and write
- **metadata**: access: read-only

#### Personal Access Token (classic) Permissions:
- **repo**


[refer](https://github.com/MyActionWay/lighthouse-badger-workflows#lighthouse-badger-easyyml:~:text=and%20permissions%20required-,PAT%20(fine%2Dgrained)%3A%20repository%20permissions,-contents%20%3D%3E%20access%3A%20read)

For more information, refer to the [GitHub documentation on using
secrets in GitHub
Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions).
2024-07-25 12:07:22 -03:00
George
16cee9c719
Avoid broken links check for video blog post 2024-07-09 12:44:13 -03:00
George
8d82670ff1
Changes to deploy-docker-tag.yml now trigger action 2024-06-19 17:17:29 -03:00
George
acdc9ff57e
Changes to deploy-image.yml now trigger action 2024-06-19 17:16:11 -03:00
George
fb67d309c9
Changes to docker-slim.yml now trigger action 2024-06-19 17:15:26 -03:00
George
1569966cf6
Bib changes now trigger build action 2024-06-19 17:13:39 -03:00
George
b723e7d917
Fixed docker-slim.yml issue 2024-06-19 15:01:27 -03:00
Tian Lan
da4486507a
Update docker-slim.yml (#2449)
Fixed a bug that causes docker-slim action to run and fail on forked
repositories. #2103
2024-05-27 13:04:02 -03:00
George
8fe4bee5e6
Remove lsi command (#2428)
Removed lsi command from code since it was added to _config.yml

---------

Signed-off-by: George Araujo <george.gcac@gmail.com>
2024-05-17 14:19:02 -03:00
George
e8f224c1be
Changing Gemfile now triggers page build 2024-05-17 10:45:29 -03:00
George
cb0db65d8c
Updated docker slim action 2024-05-06 21:15:29 -03:00
Raffaele Mancuso
492c509646
Set user agent for lychee (#2368)
See: https://github.com/alshedivat/al-folio/discussions/2366
See: https://github.com/lycheeverse/lychee/issues/1411
2024-04-24 13:17:29 -03:00
George
18f7307e07
Fixed axe workflow (#2149)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-30 15:16:15 -03:00
George
533798410e
Removing lighthouse_results from broken-links trigger 2024-01-28 20:02:15 -03:00
George
2356aea6e4
Removing lighthouse results from deploy trigger 2024-01-28 20:01:44 -03:00
George
1935a2ace0
Avoid deploying site when changes are in README files 2024-01-28 19:35:52 -03:00
George
2492ab389b
Workflow fix (#2136)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-27 22:58:40 -03:00
George
7638547a49
Updated checkout step in lighthouse-badger.yml 2024-01-23 13:08:48 -03:00
George
b83a0e38c4
Added Lighthouse test GitHub action (#2084)
Added support for Lighthouse test as a GitHub action, and it appears
like
[this](https://github.com/george-gca/multi-language-al-folio?tab=readme-ov-file#lighthouse-pagespeed-insights).
The only thing missing is for @alshedivat to create a [repository
secret](https://github.com/MyActionWay/lighthouse-badger-workflows#lighthouse-badger-easyyml)
named `LIGHTHOUSE_BADGER_TOKEN` with the information needed.

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-23 10:35:13 -03:00
George
db0a92b8d4
Moved prettier comment on PR to its own action (#2114)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-22 18:01:55 -03:00
George
bbaae0afa9
Fixed prettier actions (#2113)
After some thorough testing, finally made prettier on PR work. Since an
html file can't be used as comment on GitHub, changed to simply point to
the action that failed and to the file containing the html diff.

Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-22 17:45:34 -03:00
George
27d2fa093d
Changed how prettier comments on PR works (#2112)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-22 14:49:34 -03:00
George
7ed8f49e72
Update prettier-on-pr.yml permissions 2024-01-22 13:40:33 -03:00
George
8af6b73fd6
Prettier check now generates a diff comment on PR (#2085)
Splitted prettier GitHub action into two:
- `on push`, only runs on direct pushes, if test fails generates an
artifact (that lasts for 3 days) with an html version of the changes
needed to pass prettier test
- `on PR`, only runs on PRs, if test fails comments on the PR with the
HTML content of the diff

I couldn't actually test the `on PR` version since it needs to be on a
PR in the master branch, so this will only be triggered after this PR is
accepted, and for the next PR that fails prettier test.

PS: currently the artifact is a zip file with the html inside. It is not
currently possible to generate it other way, we have to wait for [this
issue](https://github.com/actions/upload-artifact/issues/14) to be
closed.

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-22 13:30:24 -03:00
George
67000003fa
Downgrade ruby version (#2098)
Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-19 11:45:19 -03:00
George
04f7b041a1
Changed conditions of running GitHub actions (#2082)
The GitHub actions were running everytime a new commit was made to the
repo, but that wasn't needed. For example, we don't need to try to
create a new docker image if the libraries didn't change, same to build
the whole site after a change in the README.md.

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-19 11:11:18 -03:00
George
1775a9a99d
Axe accessibility test support (#2080)
Added GitHub action to do axe accessibility tests with [axe
cli](https://github.com/dequelabs/axe-core-npm/tree/develop/packages/cli).
I believe it is best by default to let this be run only manually, since
fixing some of the issues are not straightforward (I haven't fixed them
all for this template yet).

---------

Signed-off-by: George Araújo <george.gcac@gmail.com>
2024-01-15 16:38:31 -03:00