Skip to content

Conflicts #788

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

Merged
merged 7 commits into from
Feb 27, 2021
Merged

Conflicts #788

merged 7 commits into from
Feb 27, 2021

Conversation

vybhav72954
Copy link
Collaborator

Description

Because of the multiple merge conflicts, I was forced to make a new PR.

This original PR - #760, the changes were accepted but because i deleted the local branch in my own local fork, i had to make a new PR.

Fixes #718

@HarshCasper
Copy link
Owner

Hello @sohamsshah

Can you please have a look at it once?

Copy link
Collaborator

@sohamsshah sohamsshah left a comment

Choose a reason for hiding this comment

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

Hi @vybhav72954, first of all thanks for taking time for refactoring the file/dir names. Most of the work seems good to me. Though I found some directories which were being missed out. Can you address these?

Directory Names that can be changed:

  • Go/port-scanner-go
  • Python/chromedino_script
  • Python/cryptocurrency_converter

Also, as an enhancement;
All Readme files must have README.md Name instead of readme.md or 'Readme.md` so as to have consistent naming pattern.

Changes required at:

In Go

  • Go/porter-scanner-go/Readme.md

In Javascript:

  • Automate_Tinder
  • Follow_Instagram
  • HTML_To_Markdown
  • Instagram_Like
  • Who_Don't_Follow_You

In Python also some directories do have bad naming for README.md files. Though IMO, since the directory size is too large, can be ignored for the moment OR a simple script that can rename all the bad Readme files can be also a good way to tackle this.

@HarshCasper Should we have some tests that checks the naming convention for these as well? Let me know your opinions upon this.

@vybhav72954
Copy link
Collaborator Author

vybhav72954 commented Feb 27, 2021

@sohamsshah Thanks for the Update, I actually never checked the JS and GO directory which is a shortcoming on my part.

I believe a separate script would be a good idea for README and I can make a separate issue for that, the reason I suggest we don't do any changes in the READMEs as of now because I believe that for the static website to be launched in near future, we would have to change READMEs anyway (I would be doing the same). I will change the names of the files then and there only.

A GitHub check for enforcing a naming convention is a good idea that can be explored in the future though.

Moreover, I have already mentioned the followed naming convention in the Styling Guidelines of the Project.

@vybhav72954
Copy link
Collaborator Author

The files in the Python DIctionary are newly added scripts, that's why I failed to correct them in my previous commits.

Copy link
Collaborator Author

@vybhav72954 vybhav72954 left a comment

Choose a reason for hiding this comment

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

I have made the required changes apart from README the reason for which I have explained above already.

Copy link
Collaborator

@sohamsshah sohamsshah left a comment

Choose a reason for hiding this comment

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

Sounds good to me. Thanks @vybhav72954 !

@sohamsshah sohamsshah merged commit afe471b into HarshCasper:master Feb 27, 2021
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.

Irregular Directory Names
3 participants