I eventually figured it out: I was putting the flags in the wrong section.

> On Jan 12, 2023, at 11:00 PM, Matt Sicker <m...@musigma.org> wrote:
> 
> Projects got enabled, but Issues are still pending. Maybe this will sync up 
> in the next several hours.
> —
> Matt Sicker
> 
>> On Jan 12, 2023, at 22:56, mattsic...@apache.org wrote:
>> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> mattsicker pushed a commit to branch release-2.x
>> in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
>> 
>> 
>> The following commit(s) were added to refs/heads/release-2.x by this push:
>>    new 6fc092e673 Enable GitHub issues and projects
>>    new a791477d7b Merge pull request #1200 from jvz/release-2.x
>> 6fc092e673 is described below
>> 
>> commit 6fc092e67341a037212af59effca029c6d6dbe08
>> Author: Matt Sicker <mattsic...@apache.org>
>> AuthorDate: Thu Jan 12 22:49:34 2023 -0600
>> 
>>   Enable GitHub issues and projects
>> 
>>   And update the tags. More tags.
>> ---
>> .asf.yaml | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>> 
>> diff --git a/.asf.yaml b/.asf.yaml
>> index 6d85638ba1..d3040ea441 100644
>> --- a/.asf.yaml
>> +++ b/.asf.yaml
>> @@ -24,14 +24,32 @@ notifications:
>> github:
>>  description: "Apache Log4j 2 is an upgrade to Log4j that provides 
>> significant improvements over its predecessor, Log4j 1.x, and provides many 
>> of the improvements available in Logback while fixing some inherent problems 
>> in Logback's architecture."
>>  homepage: https://logging.apache.org/log4j/2.x/
>> +  # enable GitHub Issues and Projects
>> +  issues: true
>> +  projects: true
>> +  # and enable support for our old Jira instance
>> +  autolink_jira:
>> +    - LOG4J2
>>  labels:
>>    - apache
>>    - api
>>    - java
>> +    - jvm
>>    - library
>>    - log4j
>>    - log4j2
>>    - logging
>> +    - logger
>> +    - api
>> +    - async
>> +    - asynchronous
>> +    - syslog
>> +    - structured-logging
>> +    - json
>> +    - performance
>> +    - high-performance
>> +    #  ultra-high-max-plus-performance
>> +    - concurrency
>>  protected_branches:
>>    # Prevent force pushes to primary branches
>>    master: {}
>> 
> 

Reply via email to