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

Fixed location (and name) of .perltidyrc #5835

Merged
merged 1 commit into from
Sep 27, 2023

Conversation

noctarius
Copy link
Contributor

Updated the location and name of .perltidyrc in the README

After the recent change (f172679) the location and name of perltitdyrc has changed.

Disable-check: force-changelog-file

@github-actions
Copy link

@gayyappan, @mahipv: please review this pull request.

Powered by pull-review

Copy link
Contributor

@jnidzwetzki jnidzwetzki left a comment

Choose a reason for hiding this comment

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

Looks good to me.

However, the PR message is a bit misleading. The commit f172679 did not change the name or location of the perltidyrc file. This was changed in 244b3e6.

@fabriziomello
Copy link
Contributor

Looks good to me.

However, the PR message is a bit misleading. The commit f172679 did not change the name or location of the perltidyrc file. This was changed in 244b3e6.

Oooops... my bad... send to @noctarius the wrong commit... sorry!!!

@noctarius noctarius force-pushed the update-test-readme branch from cf89639 to 8c29215 Compare June 29, 2023 20:45
@noctarius
Copy link
Contributor Author

No worries. Updated the commit message real quick.

Update the location and name of .perltidyrc in the README

After the recent change (timescale@244b3e6)
the location and name of perltitdyrc has changed.

Signed-off-by: noctarius aka Christoph Engelbert <[email protected]>
@svenklemm svenklemm merged commit 05b66ac into timescale:main Sep 27, 2023
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.

4 participants