From commits-return-87120-archive-asf-public=cust-asf.ponee.io@sling.apache.org Tue Jun 30 10:51:13 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id C1D68180643 for ; Tue, 30 Jun 2020 12:51:12 +0200 (CEST) Received: (qmail 40957 invoked by uid 500); 30 Jun 2020 10:51:12 -0000 Mailing-List: contact commits-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list commits@sling.apache.org Received: (qmail 40944 invoked by uid 99); 30 Jun 2020 10:51:12 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2020 10:51:12 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 0E563890B8; Tue, 30 Jun 2020 10:51:12 +0000 (UTC) Date: Tue, 30 Jun 2020 10:51:12 +0000 To: "commits@sling.apache.org" Subject: [sling-site] branch asf-site updated: Automatic website deployment from https://builds.apache.org/job/Sling/job/sling-site/job/master/398/ MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <159351427199.11012.1267844844571891664@gitbox.apache.org> From: git-site-role@apache.org X-Git-Host: gitbox.apache.org X-Git-Repo: sling-site X-Git-Refname: refs/heads/asf-site X-Git-Reftype: branch X-Git-Oldrev: 42e6428462f0c98242b68377ba8b765701183553 X-Git-Newrev: fd7c565b38af21f5cf4e5d02a6a689286e7c82dd X-Git-Rev: fd7c565b38af21f5cf4e5d02a6a689286e7c82dd X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/sling-site.git The following commit(s) were added to refs/heads/asf-site by this push: new fd7c565 Automatic website deployment from https://builds.apache.org/job/Sling/job/sling-site/job/master/398/ fd7c565 is described below commit fd7c565b38af21f5cf4e5d02a6a689286e7c82dd Author: jenkins AuthorDate: Tue Jun 30 10:51:07 2020 +0000 Automatic website deployment from https://builds.apache.org/job/Sling/job/sling-site/job/master/398/ --- contributing.html | 9 ++++++++- repolist.html | 3 +++ 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/contributing.html b/contributing.html index def1757..126b411 100644 --- a/contributing.html +++ b/contributing.html @@ -114,6 +114,13 @@
  • open a JIRA issue and attach your source code to it as a zip or tar archive.

    • For people who are completely new to contributing to an Apache Software Foundation project, the Get Involved page provides you with enough resources to understand how the foundation works and how its projects are structured - and don't hesitate to ask on our mailing lists!

    +

    Git

    +

    Commit meesages

    +

    For non-trivial commits a Jira issue is required. Once the Jira issue is created, the commit message must include the Jira issue key and the summary as the first line, followed by an optional description of the fix. For example:

    +

    ``` SLING-1234 - Fix NPE in FooImpl

    +

    When the FooImpl is reconfigured the bar field can be set to null, so check against null values. ```

    +

    Pull request changes

    +

    When iterating on a GitHub pull request a single commit can receive multiple follow-up fixes. To help preserve a linear history and to make changes easy to follow, please squash the changes in a single commit and force-push to the GitHub branch.

    Testing

    Each Sling module comes with an automated build, usually based on Apache Maven. Your change should be covered by new unit tests that verify that the changes work as expected.

    In case your changes are more far-reaching and the module you are contributing to is part of the Sling Starter, it is a good idea to also run the Sling Starter integration tests. This can be achieved by doing the following:

    @@ -131,7 +138,7 @@