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

Readme: fix link to RFC 004 #516

Merged
merged 2 commits into from
Jan 10, 2022
Merged

Readme: fix link to RFC 004 #516

merged 2 commits into from
Jan 10, 2022

Conversation

tdeitch
Copy link
Contributor

@tdeitch tdeitch commented Nov 8, 2021

Before this PR

The link from the readme to RFC 004 is wrong (it uses the wrong branch name).

After this PR

==COMMIT_MSG==
Readme: fix link to RFC 004
==COMMIT_MSG==

Possible downsides?

Maybe we wanted to switch the default branch in palantir/conjure instead? Either way, I think it's worth fixing this unless that is imminent.

@stale
Copy link

stale bot commented Jan 9, 2022

This PR has been automatically marked as stale because it has not been touched in the last 14 days. If you'd like to keep it open, please leave a comment or add the 'long-lived' label, otherwise it'll be closed in 7 days.

@stale stale bot added the stale label Jan 9, 2022
@tdeitch
Copy link
Contributor Author

tdeitch commented Jan 10, 2022

Still relevant!

@stale stale bot removed the stale label Jan 10, 2022
@tdeitch
Copy link
Contributor Author

tdeitch commented Jan 10, 2022

Looks like maybe checks don't work on this repo? Or do I have to do something special to make them work?

@ferozco ferozco merged commit 85ec2c1 into develop Jan 10, 2022
@ferozco ferozco deleted the td/readme-fix-rfc-link branch January 10, 2022 14:41
@ferozco
Copy link
Contributor

ferozco commented Jan 10, 2022

ya looks like something is up with the repo. I just power merged the readme change for now. @carterkozak @CRogers for SA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants