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

Developer guide: Include instructions on how to setup a sandbox folder for testing in Intellij #204

Open
yong24s opened this issue Jul 17, 2018 · 6 comments
Labels

Comments

@yong24s
Copy link
Contributor

yong24s commented Jul 17, 2018

Following v1.11 requirements, the generated report folder will be changed from reposense-report to docs.

As our documentation files are also in docs, this impedes with development and testing.

Let's move our documentation files to another folder.

@damithc
Copy link
Collaborator

damithc commented Jul 17, 2018

Not sure if this is necessary. The report should be in target-folder/docs, not necessarily {root}/docs

@yong24s
Copy link
Contributor Author

yong24s commented Jul 17, 2018

Yes. I got IntelliJ to run in a "sandboxed" folder.

I will update the developer guide to include this requirement.

Will update this issue.

@yong24s yong24s changed the title Move documentation files to another folder Developer guide: Include instructions on how to setup a sandbox folder for testing in Intellij Jul 17, 2018
@damithc damithc added the a-Docs label Jan 7, 2019
@damithc
Copy link
Collaborator

damithc commented Jan 7, 2019

@yong24s is this still applicable?

@yong24s
Copy link
Contributor Author

yong24s commented Jan 9, 2019

Yes, it is a good practice.

Background:

We clone repositories into the root of our project for testing with assumption that git-clone never fails for positive tests.

If the git-clone were to fail, the next git operation may get executed on our git working directory. This can potentially destroy our uncommitted changes.

@Tejas2805
Copy link
Contributor

@yong24s Hi, have the instructions been included? Or can I work on this issue?

@yong24s
Copy link
Contributor Author

yong24s commented Sep 22, 2019

@Tejas2805, yes you may work on this issue but I suggest you to take a look at #659 first, as the issue is better defined.

@dcshzj dcshzj moved this to For existing developers in RepoSense Roadmap Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: For developers
Development

No branches or pull requests

3 participants