Code Monkey home page Code Monkey logo

developer-toolkit-template-go's Introduction

developer-toolkit-template-go

Testing Security Scan Go Report Card GoDoc License CLA assistant Release

TODO

Find and replace all instances of developer-toolkit-template-go in ALL files with the name of your repo.

Example

// TODO

Community

New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices.

  • Roadmap - As part of the Developer Toolkit, the roadmap for this project follows the same RFC process
  • Issues or Enhancement Requests - Issues and enhancement requests can be submitted in the Issues tab of this repository. Please search for and review the existing open issues before submitting a new issue.
  • Contributors Guide - Contributions are welcome (and if you submit a Enhancement Request, expect to be invited to contribute it yourself ๐Ÿ˜).
  • Community discussion board - Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub.

Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. If you'd like to execute our corporate CLA, or if you have any questions, please drop us an email at [email protected].

Development

Requirements

  • Go 1.13.0+
  • GNU Make
  • git

Building

# Default target is 'build'
$ make

# Explicitly run build
$ make build

# Locally test the CI build scripts
# make build-ci

Testing

Before contributing, all linting and tests must pass. Tests can be run directly via:

# Tests and Linting
$ make test

# Only unit tests
$ make test-unit

# Only integration tests
$ make test-integration

Commit Messages

Using the following format for commit messages allows for auto-generation of the CHANGELOG:

Format:

<type>(<scope>): <subject>

Type Description Change log?
chore Maintenance type work No
docs Documentation Updates Yes
feat New Features Yes
fix Bug Fixes Yes
refactor Code Refactoring No

Scope

This refers to what part of the code is the focus of the work. For example:

General:

  • build - Work related to the build system (linting, makefiles, CI/CD, etc)
  • release - Work related to cutting a new release

Package Specific:

  • newrelic - Work related to the New Relic package
  • http - Work related to the internal/http package
  • alerts - Work related to the pkg/alerts package

Documentation

Note: This requires the repo to be in your GOPATH (godoc issue)

$ make docs

Support

New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR SUPPORT, although you can report issues and contribute to the project here on GitHub.

Please do not report issues with this software to New Relic Global Technical Support.

Open Source License

This project is distributed under the Apache 2 license.

developer-toolkit-template-go's People

Contributors

lucasgonze avatar nr-developer-toolkit avatar sanderblue avatar snyk-bot avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

developer-toolkit-template-go's Issues

bug: semantic PR check in CI not documented in CONTRIBUTING

Description

On submitting a PR that matches the requirements in CONTRIBUTING.md, the submitter will get a failure based on the formatting of their commit message, but the formatting is not documented.

Current behavior

CI error on PR:

=== developer-toolkit-template-go === [ lint-commit      ]: Checking that commit messages are properly formatted...
f3551e1: subject does not match regex [(chore|docs|feat|fix|refactor|tests?)\s?(\([^\)]+\))?!?: .*]
make: *** [build/lint.mk:53: lint-commit] Error 1

Expected behavior

The contributor guidelines should communicate that subject must begin with a keyword followed by a colon.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Create a commit with message "Debug"
  2. Submit PR
  3. See error relating to commit formatting

Debug Output (if applicable)

image

Additional Context

https://github.com/newrelic/developer-toolkit-template-go/actions/runs/5546108613/jobs/10125939014?pr=11

Bug: broken links in CONTRIBUTING.md

Description

CONTRIBUTING.md contains two broken links

Current behavior

Expected behavior

  1. No 404s. There do not have to be links.
  2. If there are links, they are correct.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Open repository home page at https://github.com/newrelic/developer-toolkit-template-go
  2. Click CONTRIBUTING.md, which leads to https://github.com/newrelic/developer-toolkit-template-go/blob/main/CONTRIBUTING.md
  3. See error

References or Related Issues

Are there any other related GitHub issues (open or closed) or Pull Requests that should be linked here?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.