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

Feature: clang-format action #7738

Closed
iraizo opened this issue Sep 5, 2021 · 8 comments
Closed

Feature: clang-format action #7738

iraizo opened this issue Sep 5, 2021 · 8 comments

Comments

@iraizo
Copy link
Contributor

iraizo commented Sep 5, 2021

Describe your feature request or suggestion in detail

The commits of every PR should be checked if formatted correctly according to .clang-format based on an github app/action.

Describe a possible solution to your feature or suggestion in detail

https://github.com/marketplace/actions/git-clang-format-check-per-commit

Additional context

I will try to make a pr for this, but im not sure if it is correct due to my first time using any CI really.

@iraizo
Copy link
Contributor Author

iraizo commented Sep 7, 2021

@Kitzunu @Winfidonarleyan Can one of you help me out to find the issue with the workflow crying about


Error : .github#L1
every step must define a `uses` or `run` key

https://github.com/iraizo/azerothcore-wotlk/blob/fix-issue-7738/.github/workflows/codestyle.yml

@FrancescoBorzi
Copy link
Member

maybe @locus313 can help

@patou01
Copy link
Contributor

patou01 commented Sep 18, 2021

I'm not experienced with github actions, but with some google-fu I find the following:
einaregilsson/beanstalk-deploy#2

And it seems you are doing something similar? Also might want to swap the "name" with the "uses" so the name comes first in the step, though it probably doesn't matter.
image

Maybe you could check that if nobody has given you more input?

@iraizo
Copy link
Contributor Author

iraizo commented Sep 18, 2021

That has already been fixed, im still searching for an action that fullfils its correct purpose.

@ghost ghost removed the Suggestion label Oct 5, 2021
@ghost ghost closed this as completed Oct 5, 2021
@iraizo iraizo reopened this Oct 5, 2021
@Kitzunu
Copy link
Member

Kitzunu commented Jan 9, 2022

closing as we dropped clang-format

@Kitzunu Kitzunu closed this as completed Jan 9, 2022
@iraizo
Copy link
Contributor Author

iraizo commented Jan 9, 2022

closing as we dropped clang-format

Why is that?

@Kitzunu
Copy link
Member

Kitzunu commented Jan 9, 2022

because it only caused problems and changed code around to things that were not our standard. #9934

It was introduced before being ready and up to the job of our standards. Until then, having to always press ctrl z to remove what it does just isn't time efficient

@iraizo
Copy link
Contributor Author

iraizo commented Jan 9, 2022

Good job to the nice workflow you and others introduced that allowed the merge then if it wasnt that ready even you literally reviewed it to be "ready".

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

No branches or pull requests

4 participants