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

Link is 404 on website #854

Open
laglangyue opened this issue Apr 4, 2024 · 6 comments
Open

Link is 404 on website #854

laglangyue opened this issue Apr 4, 2024 · 6 comments

Comments

@laglangyue
Copy link

https://github.com/scalameta/mdoc/settings/secrets

because user can't visit it.
Can we provide a shutscreen?

@laglangyue laglangyue changed the title Link is 404 on websit Link is 404 on website Apr 4, 2024
@tgodzik
Copy link
Contributor

tgodzik commented Apr 4, 2024

Why would you want to access secrets of the current repository? It's not available on purpose

@laglangyue
Copy link
Author

I don't want to access to secrets of the current repository.

When I configure according to the official website documentation, this link is a 404, and I don't know how to configure it. Very bad

image

@laglangyue
Copy link
Author

so I mean that, maybe we can provide that a screenshot of it, put on a mosaic.
And then, the guideline will be clear

@laglangyue
Copy link
Author

Or we can change the link https://github.com/scalameta/mdoc/settings/secrets to https://github.com/${user_name}/${repository_name}/settings/secrets

@tgodzik
Copy link
Contributor

tgodzik commented Apr 4, 2024

Sure, that's a good idea, would you mind changing it?

@laglangyue
Copy link
Author

It's not that I'm unwilling now, I've submitted many PRs to scalajdbc and pekko before.

Actually I am learning the of git action and sbt-mdoc, I have completed 80% of the deployment,
https://github.com/laglangyue/laglang-note
and if I can complete it, I will submit a PR later.

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

No branches or pull requests

2 participants