https://acmestack.com/docs/contributing/Recent content in Contributing onHugo -- gohugo.ioen-USTue, 06 Oct 2020 08:49:15 +0000https://acmestack.com/docs/contributing/guide/Tue, 06 Oct 2020 08:49:31 +0000https://acmestack.com/docs/contributing/guide/This guide is for contributors who already have a pull request to submit. First-time contributors should head to the Contributor Guide to get started, and the Contributor Guide also applies to all developers. Let’s start from developer-environment-settinghttps://acmestack.com/docs/contributing/developer-environment-setting/Thu, 12 Nov 2020 13:26:54 +0100https://acmestack.com/docs/contributing/developer-environment-setting/the example for goland Copyright # Copy all with format Licensed to the AcmeStack under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.https://acmestack.com/docs/contributing/contributor-license-agreement/Thu, 12 Nov 2020 13:26:54 +0100https://acmestack.com/docs/contributing/contributor-license-agreement/How do I sign? # After creating your first Pull Request the CLA assistant bot will respond with information regarding your CLA status along with a link to sign the CLA. make sure the git config user.name same for GitHub name. reply the message I have read the CLA Document and I hereby sign the CLA to sign CLA. and reply the messasge recheck to check the sign statehttps://acmestack.com/docs/contributing/github-workflow-guide/Thu, 12 Nov 2020 13:26:54 +0100https://acmestack.com/docs/contributing/github-workflow-guide/1. Fork in the cloud # Visit https://github.com/acmestack Choose one project Click Fork button (top right) to establish a cloud-based fork. 2. Clone fork to local storage # Per Go’s workspace instructions, place project’ code on your GOPATH using the following cloning procedure. git clone git@github.com:<your_name>/{project-name}.git 3. Set remote repository to sync updates # git remote add upstream https://github.com/acmestack/{project-name}.git Keep your branch in sync # You will need to periodically fetch changes from the upstream repository to keep your working branch in sync.https://acmestack.com/docs/contributing/coding-conventions/Thu, 12 Nov 2020 13:26:54 +0100https://acmestack.com/docs/contributing/coding-conventions/Go Go Code Review Comments Effective Go Know and avoid Go landmines Comment your code. Go’s commenting conventions If reviewers ask questions about why the code is the way it is, that’s a sign that comments might be helpful. Command-line flags should use dashes, not underscores Naming Please consider package name when selecting an interface name, and avoid redundancy. For example, storage.Interface is better than storage.StorageInterface. Do not use uppercase characters, underscores, or dashes in package names.https://acmestack.com/docs/contributing/pull-requests/Tue, 06 Oct 2020 08:49:31 +0000https://acmestack.com/docs/contributing/pull-requests/Before You Submit a Pull Request # This guide is for contributors who already have a pull request to submit. First-time contributors should head to the Contributor Guide to get started, and the Contributor Guide also applies to all developers. Make sure your pull request adheres to our best practices. These include following project conventions, making small pull requests, and commenting thoroughly. Please read the more detailed section on Best Practices for Faster Reviews at the end of this doc.https://acmestack.com/docs/contributing/testing-guide/Tue, 06 Oct 2020 08:49:31 +0000https://acmestack.com/docs/contributing/testing-guide/TODO