feat(homepage): add git button and split css styles #1

Merged
aleksa merged 9 commits from dev into main 2026-08-17 16:43:56 +00:00
Owner
  • Added a git button to link to my personal git profile (this one!).
  • Split global.css into global.css and homepage.css to prevent global getting cluttered with single-use elements.
- Added a git button to link to my personal git profile (this one!). - Split global.css into global.css and homepage.css to prevent global getting cluttered with single-use elements.
aleksa self-assigned this 2025-04-17 01:35:47 +00:00
feat(homepage): add git button and split css styles
All checks were successful
E2E Tests with Cypress / cypress (push) Successful in 3m7s
E2E Tests with Cypress / cypress (pull_request) Successful in 2m58s
1e443c6b43
ci: remove redundant push trigger for main
All checks were successful
E2E Tests with Cypress / cypress (push) Successful in 3m4s
E2E Tests with Cypress / cypress (pull_request) Successful in 3m4s
2fccb3bb56
Author
Owner
  • Removed main branch push trigger as pushing to main directly will not be happening. It was accidentally left in from me testing the workflow on another test repo. Also included in this PR since it is very minor.
- Removed main branch push trigger as pushing to main directly will not be happening. It was accidentally left in from me testing the workflow on another test repo. Also included in this PR since it is very minor.
fix(layout): use dvh to prevent mobile scroll issues
All checks were successful
E2E Tests with Cypress / cypress (push) Successful in 3m4s
E2E Tests with Cypress / cypress (pull_request) Successful in 3m0s
3770e67898
Author
Owner
  • Switched vh to dvh to prevent the page being too long vertically on mobile due to the browser and other mobile UI elements stealing screen real estate.
- Switched vh to dvh to prevent the page being too long vertically on mobile due to the browser and other mobile UI elements stealing screen real estate.
Author
Owner

I need to add more Cypress tests for the new element. This will become a regular thing where i add e2e tests for every addition to make sure the test coverage is as high as possible. I will do the same thing when I start incorporating more testing types.

I tried using the default Cypress hover event to test the button changing style on hover but it doesn't work properly, so I will get cypress-real-events to enable better e2e test interactions. This was recommended by most people complaining about default Cypress event implementations since they just use JS to simulate events instead of executing them natively.

I need to add more Cypress tests for the new element. This will become a regular thing where i add e2e tests for every addition to make sure the test coverage is as high as possible. I will do the same thing when I start incorporating more testing types. I tried using the default Cypress hover event to test the button changing style on hover but it doesn't work properly, so I will get `cypress-real-events` to enable better e2e test interactions. This was recommended by most people complaining about default Cypress event implementations since they just use JS to simulate events instead of executing them natively.
Author
Owner

cypress-real-events works for hovering and the style change is visible in the video, but cy.screenshot() doesn't capture it. I am looking into this for a while now but there doesn't seem to be a solution and even the official documentation for cypress-real-events says so: realHover explanation.

I hope to find a different solution for testing hover since I do not want to force a CSS change as it is usually done but I want to simulate a real hover somehow. If it proves to be impossible tho, I might just stick to adding hover as a class.

`cypress-real-events` works for hovering and the style change is visible in the video, but `cy.screenshot()` doesn't capture it. I am looking into this for a while now but there doesn't seem to be a solution and even the official documentation for `cypress-real-events` says so: [realHover explanation](https://github.com/dmtrKovalenko/cypress-real-events?tab=readme-ov-file#1-why-cyrealhover-hovering-state-does-not-show-in-the-visual-regression-services). I hope to find a different solution for testing hover since I do not want to force a CSS change as it is usually done but I want to simulate a real hover somehow. If it proves to be impossible tho, I might just stick to adding `hover` as a class.
feat: build terminal portfolio foundation
All checks were successful
Quality and Cypress / quality (push) Successful in 6s
Quality and Cypress / quality (pull_request) Successful in 2s
Quality and Cypress / cypress (push) Successful in 1m11s
Quality and Cypress / cypress (pull_request) Successful in 3s
756c6ca4ed
feat: complete interactive terminal experience
All checks were successful
Quality and Cypress / quality (push) Successful in 3s
Quality and Cypress / quality (pull_request) Successful in 2s
Quality and Cypress / cypress (push) Successful in 1m0s
Quality and Cypress / cypress (pull_request) Successful in 3s
9606fd084a
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Steps referencing the unsupported `forgejo.run_id` context were dropped
silently by the runner, so the quality gate and the whole Cypress phase
never executed while the run still reported success. Use the GITHUB_RUN_ID
environment variable instead.

Also stop leaking state between runs: use a fixed compose project name and
tear down leftovers before starting, wait via `compose up --wait` instead
of a hand written poll loop, and copy artifacts out of the Cypress
container so the runner workspace keeps no root owned files.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ci: deploy to production on push to main
Some checks failed
Quality and Cypress / quality (push) Successful in 54s
Quality and Cypress / quality (pull_request) Successful in 2s
Quality and Cypress / cypress (push) Failing after 1m22s
Quality and Cypress / cypress (pull_request) Failing after 54s
932e0dcdbe
Runs the quality gate, then updates the deployment checkout on the server
and rebuilds the app-prod compose service. The image is built before the
running container is replaced, and a failed health check or smoke test
restores the previously deployed image.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ci: keep cypress artifacts for a single day
Some checks failed
Quality and Cypress / cypress (push) Blocked by required conditions
Quality and Cypress / quality (push) Has been cancelled
Quality and Cypress / quality (pull_request) Successful in 43s
Quality and Cypress / cypress (pull_request) Successful in 1m21s
387e4d7c22
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ci: keep cypress artifacts for five days
Some checks failed
Quality and Cypress / cypress (push) Blocked by required conditions
Quality and Cypress / quality (push) Has been cancelled
Quality and Cypress / quality (pull_request) Successful in 43s
Quality and Cypress / cypress (pull_request) Successful in 1m19s
22c0ba710c
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
aleksa force-pushed dev from 22c0ba710c
Some checks failed
Quality and Cypress / cypress (push) Blocked by required conditions
Quality and Cypress / quality (push) Has been cancelled
Quality and Cypress / quality (pull_request) Successful in 43s
Quality and Cypress / cypress (pull_request) Successful in 1m19s
to 90cae95847
All checks were successful
Quality and Cypress / quality (push) Successful in 2s
Quality and Cypress / quality (pull_request) Successful in 2s
Quality and Cypress / cypress (push) Successful in 53s
Quality and Cypress / cypress (pull_request) Successful in 53s
2026-08-17 16:34:09 +00:00
Compare
Author
Owner

Came back to the project and speedran setup.

Came back to the project and speedran setup.
aleksa merged commit 157f93732f into main 2026-08-17 16:43:56 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aleksa/aleksa.sh!1
No description provided.