<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:58:33 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[DOCS-58] Linting of a docs project job should be done on files within the patchset</title>
                <link>https://jira.opendaylight.org/browse/DOCS-58</link>
                <project id="10121" key="DOCS">docs</project>
                    <description>&lt;p&gt;For a docs project job, the linter (coala) checks should be applied only to the files within the patchset and not on other files.&lt;/p&gt;

&lt;p&gt;For other projects with rst files, the linter (coala) should be applied and prevent files with errors and applicable warnings from being merged.&lt;/p&gt;</description>
                <environment></environment>
        <key id="29014">DOCS-58</key>
            <summary>Linting of a docs project job should be done on files within the patchset</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="6" iconUrl="https://jira.opendaylight.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="zxiiro">Thanh Ha (zxiiro)</assignee>
                                    <reporter username="klou">Kit Lou</reporter>
                        <labels>
                    </labels>
                <created>Thu, 21 Dec 2017 03:02:50 +0000</created>
                <updated>Tue, 6 Mar 2018 20:54:29 +0000</updated>
                            <resolved>Tue, 6 Mar 2018 20:54:29 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="60570" author="zxiiro" created="Wed, 27 Dec 2017 16:34:47 +0000"  >&lt;p&gt;This is not possible today unless someone wants to work with upstream likely Coala project and whatever specific linters we&apos;re using to add such a feature.&lt;/p&gt;

&lt;p&gt;Personally I prefer that it scans all of the files for every run to prevent a situation where we&apos;re not following spec in some files that haven&apos;t been touched in awhile. This ensures that when we upgrade linter versions that we are always following the latest best practices. Individual files can be ignored by the linter via the excludes line as a last resort.&lt;/p&gt;</comment>
                            <comment id="60652" author="zxiiro" created="Tue, 9 Jan 2018 20:23:42 +0000"  >&lt;p&gt;We decided to look into splitting the docs verify job to individual projects at some point in the future.&lt;/p&gt;</comment>
                            <comment id="61470" author="clavoy" created="Tue, 6 Mar 2018 20:54:29 +0000"  >&lt;p&gt;Splitting out the submodules, which should help with this issue.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0395b:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>