<feed xmlns='http://www.w3.org/2005/Atom'>
<title>packages/.github/ISSUE_TEMPLATE, branch master</title>
<subtitle>Mirror of packages feed</subtitle>
<id>https://git.openwrt.org/feed/packages/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/feed/packages/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/'/>
<updated>2025-06-03T06:51:43Z</updated>
<entry>
<title>github: Add fields to help users in the bug report</title>
<updated>2025-06-03T06:51:43Z</updated>
<author>
<name>Wesley Gimenes</name>
</author>
<published>2025-06-03T06:19:29Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=38b89da400f900241b1b9eb0d20d62a199acb160'/>
<id>urn:sha1:38b89da400f900241b1b9eb0d20d62a199acb160</id>
<content type='text'>
Not everyone filling out the bug report is an expert.
These fields, with additional explanations, can hopefully
help users provide more accurate information.

Add fields to guide users in completing the bug report.

Signed-off-by: Wesley Gimenes &lt;wehagy@proton.me&gt;
</content>
</entry>
<entry>
<title>github: require user to check all bug report fields</title>
<updated>2025-06-03T06:51:43Z</updated>
<author>
<name>Wesley Gimenes</name>
</author>
<published>2025-06-03T06:08:08Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=c323222c63f39f0d57c6ad196121ab28f83e3ff2'/>
<id>urn:sha1:c323222c63f39f0d57c6ad196121ab28f83e3ff2</id>
<content type='text'>
Previously, users could leave fields blank,
resulting in missing information in the bug report.
Now, it is mandatory for all fields to be filled out,
ensuring that no essential information is overlooked.

Signed-off-by: Wesley Gimenes &lt;wehagy@proton.me&gt;
</content>
</entry>
<entry>
<title>github: Creating issue: Add external links</title>
<updated>2025-06-03T05:59:41Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2025-06-02T10:03:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=1f189894dcf334ed7afa48b1da66dac17bf14cb9'/>
<id>urn:sha1:1f189894dcf334ed7afa48b1da66dac17bf14cb9</id>
<content type='text'>
This is heavily inspired by OpenWrt main repository [1]
as in the packages feed we would like to follow
and be in sync with the main repository.

Having external, well, contact links, where users
can ask or propose feature request and even find links
for documentation or contacting us is a good idea.
Might help to improve the current state of this repository.

[1] https://github.com/openwrt/openwrt/blob/57c104ef7f8619d48579ada5ab24f78984391edd/.github/ISSUE_TEMPLATE/config.yml

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
</content>
</entry>
<entry>
<title>github: Use GitHub Issue Forms with yaml</title>
<updated>2025-06-03T05:59:41Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2025-06-02T10:38:18Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=67dc75f94138768f13ceb330fd989718272d5ad0'/>
<id>urn:sha1:67dc75f94138768f13ceb330fd989718272d5ad0</id>
<content type='text'>
This replaces the old issue templates with the new one.
It is going to reflect changes and require more details.

Issue Forms as also used in the main repository and in LuCI,
it helps users to create structured issue.

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
</content>
</entry>
</feed>
