awesome-devtools VS p6-projen-project-awesome-list

awesomedevtools and /uses are two good ones.

Working on Awesome Devtools this past week, I decided to make the repo public so others could contribute to it. I had one slight problem though, I had committed my .env file which contained secrets I would rather the world not know.

Awesome resource; I've added one of my productivity tools to it in https://github.com/sgolovine/awesome-devtools/pull/6

import { cdk } from "projen"; const project = new cdk.JsiiProject({ name: "p6-projen-project-awesome-list", author: "Philip M. Gollucci", authorAddress: "[email protected]", repositoryUrl: "https://github.com/p6m7g8/p6-projen-project-awesome-list.git", description: "Projen External Project for awesome-lists", stability: "experimental", keywords: ["awesome lists", "projen", "list", "awesome", "constructs"], defaultReleaseBranch: "main", projenrcTs: true, gitpod: true, devContainer: true, codeCov: true, prettier: true, releaseFailureIssue: true, autoApproveUpgrades: true, autoApproveOptions: { allowedUsernames: ["p6m7g8-automation"], }, deps: ["projen@^0.53.14"], peerDeps: ["projen@^0.53.14"], publishToPypi: { distName: "p6-projen-project-awesome-list", module: "p6_projen_project_awesome_list", }, publishToMaven: { javaPackage: "com.github.p6m7g8.P6ProjectProjenAwesomeList", mavenGroupId: "com.github.p6m7g8", mavenArtifactId: "p6-projen-project-awesome-list", }, publishToNuget: { dotNetNamespace: "P6m7g8.P6AwesomeList", packageId: "P6m7g8.P6AwesomeList", }, publishToGo: { moduleName: "github.com/p6m7g8/p6-projen-project-awesome-list", // why doesn't this default to repositoryUrl? }, }); project.synth();