Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update traficom contact info #1458

Merged
merged 2 commits into from
Jan 21, 2025

Conversation

Riippi
Copy link
Contributor

@Riippi Riippi commented Jan 2, 2025

Description

Add Traficom contact info to accessibility statement. There was no section for contact info (and description about it) so I added it to the same place where it is in other projects.

Related Issue

https://helsinkisolutionoffice.atlassian.net/browse/RATY-160

Motivation and Context

How Has This Been Tested?

Locally

Demos:

Links to demos are in the comments

Screenshots (if appropriate):

Screenshot 2025-01-02 at 16 01 43

Add to changelog

  • Added needed line to changelog

Copy link

github-actions bot commented Jan 2, 2025

Test Results

  1 files   68 suites   14m 23s ⏱️
 86 tests  86 ✅ 0 💤 0 ❌
172 runs  172 ✅ 0 💤 0 ❌

Results for commit 7b5e5c2.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Jan 2, 2025

Preview found from hds-demo docs/preview_1458

Demos

Docs
Core Storybook
React Storybook

@timwessman timwessman force-pushed the chore/RATY-160-update-traficom-info branch from 447e571 to 7b5e5c2 Compare January 10, 2025 08:09
Copy link
Contributor

@mrTuomoK mrTuomoK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good 👍

@Riippi Riippi merged commit 62aee43 into development Jan 21, 2025
8 checks passed
@Riippi Riippi deleted the chore/RATY-160-update-traficom-info branch January 21, 2025 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants