nikcio opened a new issue, #648:
URL: https://github.com/apache/lucenenet/issues/648

   Hi I'm new to this repository.
   
   Therefore to avoid PR spamming I would like to hear what kinds of PR's you'd 
like to get on this repository. In my own fork I've tried implementing the 
following tools/fixes/updates that might be useful to have in the main 
repository:
   
   - Dependency updates (Newtonsoft.Json) #647 
   - Dependency updates of other outdated dependencies
   - Dependabot (To check dependencies)
   - CodeQL (To check for security vulnerabilities)
   - SonarCloud (To check code quality and find security vulnerabilities)
   - Fix to vulnerability: https://github.com/nikcio/lucenenet/pull/1
   
   Other fixes/updates I have in mind
   - Fix to other vulnerabilities ([SonarCloud 
reported](https://sonarcloud.io/project/issues?resolved=false&types=VULNERABILITY&id=nikcio_lucenenet))
   - Fix SonarCloud reported 
[Bugs](https://sonarcloud.io/project/issues?resolved=false&types=BUG&id=nikcio_lucenenet)
   - Review and possibility fix [security 
hotspots](https://sonarcloud.io/project/security_hotspots?id=nikcio_lucenenet) 
reported by SonarCloud
   - Fix [code 
smells](https://sonarcloud.io/project/issues?resolved=false&types=CODE_SMELL&id=nikcio_lucenenet)
 in the project
   - Into guide to setting up the project in VS 2022 (This was quite a 
challenge because of the old frameworks used. BTW I also experience VS 
tools/analyzers crashing when I open the project 😅 So this might also be a 
reason the repository doesn't get many new contributors)
   
   Please let me know what you'd like PR's on.
   
   @NightOwl888 @rclabo you guys seems to be some of the more active 
contributors 😄 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@lucenenet.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to